search for: fragmentation

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

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

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>

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

...nd-line option. I've noticed there is some 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 (nu...

...> > \end{lstlisting} > > > > > > > > > > +\subsubsection{Datagram Sockets}\label{sec:Device Types / Socket Device / Device Operation / Datagram Sockets} > > > > > + > > > > > +\drivernormative{\paragraph}{Device Operation: Packet Fragmentation}{Device Types / Socket Device / Datagram Sockets / Fragmentation} > > > > > + > > > > > +Drivers MAY disassemble packets into smaller fragments. If drivers fragment a > > > > > +packet, they MUST follow the fragmentation rules described in section > &...

...> > \end{lstlisting} > > > > > > > > > > +\subsubsection{Datagram Sockets}\label{sec:Device Types / Socket Device / Device Operation / Datagram Sockets} > > > > > + > > > > > +\drivernormative{\paragraph}{Device Operation: Packet Fragmentation}{Device Types / Socket Device / Datagram Sockets / Fragmentation} > > > > > + > > > > > +Drivers MAY disassemble packets into smaller fragments. If drivers fragment a > > > > > +packet, they MUST follow the fragmentation rules described in section > &...

...gt; > > > > > > > > > > > +\subsubsection{Datagram Sockets}\label{sec:Device Types / Socket Device / Device Operation / Datagram Sockets} > > > > > > > + > > > > > > > +\drivernormative{\paragraph}{Device Operation: Packet Fragmentation}{Device Types / Socket Device / Datagram Sockets / Fragmentation} > > > > > > > + > > > > > > > +Drivers MAY disassemble packets into smaller fragments. If drivers fragment a > > > > > > > +packet, they MUST follow the fragmentation rul...

Hi all, At the recent LLVM developers' meeting, I presented 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.

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

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:

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 generation for packet sockets > and tap/ma...

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 generation for packet sockets > and tap/ma...

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 at 02:47:54AM +0000, Ben Hutchings wrote: > >>>>>>>>> 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...

..., 2015 at 02:47:54AM +0000, Ben Hutchings wrote: > >>>>>>>>> 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...

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

Hello all, I understand that relatively high fragmentation is inherent to ZFS due to its COW and possible intermixing of metadata and data blocks (of which metadata path blocks are likely to expire and get freed relatively quickly). I believe it was sometimes implied on this list that such fragmentation for "static" data can be currently comb...

...Tue, Jan 27, 2015 at 02:47:54AM +0000, Ben Hutchings wrote: > > > > > >>> 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...

...Tue, Jan 27, 2015 at 02:47:54AM +0000, Ben Hutchings wrote: > > > > > >>> 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...