lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 22 Apr 2016 05:39:40 -0700 From: Eric Dumazet <eric.dumazet@...il.com> To: Steffen Klassert <steffen.klassert@...unet.com> Cc: Sowmini Varadhan <sowmini.varadhan@...cle.com>, netdev@...r.kernel.org Subject: Re: [RFC PATCH] gro: Partly revert "net: gro: allow to build full sized skb" On Fri, 2016-04-22 at 11:13 +0200, Steffen Klassert wrote: > On Thu, Apr 21, 2016 at 05:59:06AM -0700, Eric Dumazet wrote: > > Here at Google, we increased MAX_SKB_FRAGS, but this is a rather > > intrusive change to be upstreamed :( > > I've played here with MAX_SKB_FRAGS too, but it seems to > be device specific how many page fragments it can handle. > I wonder if we could increase MAX_SKB_FRAGS at the GRO > layer and let GSO split this buffer in something that > the transmitting device can handle? Yes, the same principle would apply. Split a GRO packet into X TSO packets with whatever number of frags. bnx2x has to linearize some skbs having more than 13 frags.
Powered by blists - more mailing lists