search for: fragmented

Displaying 20 results from an estimated 3593 matches for "fragmented".

2007 May 13
3
Fragment interface on Intel
Hi It seem that the fragment interface on certain plugins exceeds the amount of fragment operations possible on Intel GMA cards. This only occurs with the "water" and "blur" plugins. the plugins activate OK and do not report a missing GL_ARB_fragment_program in the server extensions. Waves appear when I use the water plugin with <Super><Ctrl> but there is no
2009 Apr 08
3
Rails 2.3 memcache performance drop
After much effort I upgraded our fairly large Rails app from 2.1 to 2.3. After deployment yesterday I noticed an across the board increase in response times. It seems that every call to memcache now takes 10x longer than before. Here are some example numbers from my development log (below), with memcache running locally. We see similar scale of performance drop in production as well - average
2013 Nov 28
4
[PATCH net] xen-netback: fix fragment detection in checksum setup
The code to detect fragments in checksum_setup() was missing for IPv4 and too eager for IPv6. (It transpires that Windows seems to send IPv6 packets with a fragment header even if they are not a fragment - i.e. offset is zero, and M bit is not set). Signed-off-by: Paul Durrant <paul.durrant@citrix.com> Cc: Wei Liu <wei.liu2@citrix.com> Cc: Ian Campbell <ian.campbell@citrix.com>
2011 Apr 12
3
New video card; wine freezing
Hello, I want to play Eve Online in Wine. It was working (mostly) on my old card, a GTX 280, using the nvidia driver. It was the 3rd card I've had from Nvidia in a row with manufacturing defects, so I bought a Radeon 6870, which is working good except with Wine. I am using fglrx, and have a dual head setup using xrandr. When I log in, I get to the screen where it is entering the game after I
2006 Sep 13
2
File fragmentation
...e penalty for very large files (35GB-50GB). The penalty is relatively small based on my 'intuitive' measurements.read me watching without running a real timer. The difference is very small compared to what happens after a few weeks without the fragmentation patch. Our SAN was becoming so fragmented that we were only getting 10% of normal throughput. Since we've applied this patch our SAN is continuously getting maximum throughput. Benchmarks are numbers such as 10MB/sec throughput due to fragmentation versus 90MB-150MB without fragmentation (numbers reported by telnet sessions to the SA...
2023 Sep 02
0
[PATCH] virtio-vsock: add VIRTIO_VSOCK_F_DGRAM feature bit
...hdr. \field{len} MUST equal the length of the fragment payload > > > > > +only. > > > > > > > > what does this mean exactly? > > > > > > > > > > It means that len only accounts for the fragment and not the whole > > > (fragmented) packet. The second sentence means that the virtqueue buffer > > > starts with the header. > > > > > > For virtio-net mergable RX buffers the header is only in the first > > > buffer and the length field accounts for the entire fragmented packet > > > (...
2023 Sep 02
0
[PATCH] virtio-vsock: add VIRTIO_VSOCK_F_DGRAM feature bit
...hdr. \field{len} MUST equal the length of the fragment payload > > > > > +only. > > > > > > > > what does this mean exactly? > > > > > > > > > > It means that len only accounts for the fragment and not the whole > > > (fragmented) packet. The second sentence means that the virtqueue buffer > > > starts with the header. > > > > > > For virtio-net mergable RX buffers the header is only in the first > > > buffer and the length field accounts for the entire fragmented packet > > > (...
2023 Sep 06
0
[PATCH] virtio-vsock: add VIRTIO_VSOCK_F_DGRAM feature bit
...t; > > > > > +only. > > > > > > > > > > > > what does this mean exactly? > > > > > > > > > > > > > > > > It means that len only accounts for the fragment and not the whole > > > > > (fragmented) packet. The second sentence means that the virtqueue buffer > > > > > starts with the header. > > > > > > > > > > For virtio-net mergable RX buffers the header is only in the first > > > > > buffer and the length field accounts for the e...
2020 Oct 12
2
Fragmented DWARF
...resented a lightning talk on an approach to reduce the amount of dead debug data left in an executable following operations such as --gc-sections and duplicate COMDAT removal. In that presentation, I presented some figures based on linking a game that had been built by our downstream clang port and fragmented using the described approach. Since recording the presentation, I ran the same experiment on a clang package (this time built with a GCC version). The comparable figures are below: Link-time speed (s): +--------------------+-------+---------------+------+------+------+------+------+ | Package vari...
2017 Aug 26
5
[PATCH 1/2] builder/templates/debian.preseed: enable serial console
Also unify .index-fragment files --- builder/templates/debian-7.index-fragment | 7 ------- builder/templates/debian-8.index-fragment | 7 ------- builder/templates/debian-9.index-fragment | 18 ++++++------------ builder/templates/debian.preseed | 1 + builder/templates/make-template.ml | 6 ------ 5 files changed, 7 insertions(+), 32 deletions(-) diff --git
2014 Nov 11
0
[Bug 987] New: nf_conntrack_reasm.c : Silent discard of overlapping fragments is not silent
https://bugzilla.netfilter.org/show_bug.cgi?id=987 Bug ID: 987 Summary: nf_conntrack_reasm.c : Silent discard of overlapping fragments is not silent Product: netfilter/iptables Version: unspecified Hardware: x86_64 OS: Debian GNU/Linux Status: NEW Severity: normal Priority:
2015 Jan 27
3
[PATCH 1/3] ipv6: Select fragment id during UFO/GSO segmentation if not set.
On Mon, 2015-01-26 at 09:37 -0500, Vladislav Yasevich wrote: > If the IPv6 fragment id has not been set and we perform > fragmentation due to UFO, select a new fragment id. > When we store the fragment id into skb_shinfo, set the bit > in the skb so we can re-use the selected id. > This preserves the behavior of UFO packets generated on the > host and solves the issue of id
2015 Jan 27
3
[PATCH 1/3] ipv6: Select fragment id during UFO/GSO segmentation if not set.
On Mon, 2015-01-26 at 09:37 -0500, Vladislav Yasevich wrote: > If the IPv6 fragment id has not been set and we perform > fragmentation due to UFO, select a new fragment id. > When we store the fragment id into skb_shinfo, set the bit > in the skb so we can re-use the selected id. > This preserves the behavior of UFO packets generated on the > host and solves the issue of id
2004 Feb 25
4
[Bug 48] conntrack breaks udp path mtu discovery
https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=48 ------- Additional Comments From tatonet@tiscali.it 2004-02-25 15:05 ------- I know that this is an old bug report, but it's still opened... If we save the size of each single fragment we have to face another problem: how should we re-fragment the packet if original fragments were partially or totally overlapped?
2015 Jan 28
2
[PATCH 1/3] ipv6: Select fragment id during UFO/GSO segmentation if not set.
...> patch both kernels in your case - non gso frames would still get the > > fragmentation id generated in the host kernel. > > Why would non-gso frames need a frag id? We are talking only UDP IPv6 > here, so there is no frag id generation if the packet does't need to > be fragmented. E.g. raw sockets still can generate fragments locally. It is also a valid setup to have multiple interfaces in one machine, one that is UFO enabled and one that isn't. In that case, fragmentation id generation happens on different hosts which I want to avoid. I haven't looked closely but...
2015 Jan 28
2
[PATCH 1/3] ipv6: Select fragment id during UFO/GSO segmentation if not set.
...> patch both kernels in your case - non gso frames would still get the > > fragmentation id generated in the host kernel. > > Why would non-gso frames need a frag id? We are talking only UDP IPv6 > here, so there is no frag id generation if the packet does't need to > be fragmented. E.g. raw sockets still can generate fragments locally. It is also a valid setup to have multiple interfaces in one machine, one that is UFO enabled and one that isn't. In that case, fragmentation id generation happens on different hosts which I want to avoid. I haven't looked closely but...
1999 Mar 25
0
(Fwd) DoS for Linux 2.1.89 - 2.2.3: 0 length fragment bug
Pulled from Bugtraq. Dan ____________________________________________________________________________ Dan Yocum | Phone: (630) 840-8525 Computing Division OSS/FSS | Fax: (630) 840-6345 .~. L Fermi National Accelerator Lab | email: yocum@fnal.gov /V\ I P.O. Box 500 | WWW: www-oss.fnal.gov/~yocum/ // \\ N Batavia, IL
2012 Jan 07
14
zfs defragmentation via resilvering?
...then clearing the original pools and sending the data back. This is time-consuming, disruptive and requires lots of extra storage idling for this task (or at best - for backup purposes). I wonder how resilvering works, namely - does it write blocks "as they were" or in an optimized (defragmented) fashion, in two usecases: 1) Resilvering from a healthy array (vdev) onto a spare drive in order to replace one of the healthy drives in the vdev; 2) Resilvering a degraded array from existing drives onto a new drive in order to repair the array and make it redundant again. Also, are...
2015 Jan 28
7
[PATCH 1/3] ipv6: Select fragment id during UFO/GSO segmentation if not set.
Hi, On Mi, 2015-01-28 at 11:46 +0200, Michael S. Tsirkin wrote: > On Wed, Jan 28, 2015 at 09:25:08AM +0100, Hannes Frederic Sowa wrote: > > Hello, > > > > On Di, 2015-01-27 at 18:08 +0200, Michael S. Tsirkin wrote: > > > On Tue, Jan 27, 2015 at 05:02:31PM +0100, Hannes Frederic Sowa wrote: > > > > On Di, 2015-01-27 at 09:26 -0500, Vlad Yasevich wrote:
2015 Jan 28
7
[PATCH 1/3] ipv6: Select fragment id during UFO/GSO segmentation if not set.
Hi, On Mi, 2015-01-28 at 11:46 +0200, Michael S. Tsirkin wrote: > On Wed, Jan 28, 2015 at 09:25:08AM +0100, Hannes Frederic Sowa wrote: > > Hello, > > > > On Di, 2015-01-27 at 18:08 +0200, Michael S. Tsirkin wrote: > > > On Tue, Jan 27, 2015 at 05:02:31PM +0100, Hannes Frederic Sowa wrote: > > > > On Di, 2015-01-27 at 09:26 -0500, Vlad Yasevich wrote: