| 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
| ||
|
Message-ID: <1414725541.499.3.camel@edumazet-glaptop2.roam.corp.google.com> Date: Thu, 30 Oct 2014 20:19:01 -0700 From: Eric Dumazet <eric.dumazet@...il.com> To: Or Gerlitz <gerlitz.or@...il.com> Cc: Or Gerlitz <ogerlitz@...lanox.com>, "David S. Miller" <davem@...emloft.net>, Linux Netdev List <netdev@...r.kernel.org>, Matan Barak <matanb@...lanox.com>, Amir Vadai <amirv@...lanox.com>, Saeed Mahameed <saeedm@...lanox.com>, Shani Michaeli <shanim@...lanox.com>, Ido Shamay <idos@...lanox.com> Subject: Re: [PATCH net-next 5/8] net/mlx4_en: Remove redundant code from RX/GRO path On Fri, 2014-10-31 at 01:25 +0200, Or Gerlitz wrote: > On Thu, Oct 30, 2014 at 9:00 PM, Eric Dumazet <eric.dumazet@...il.com> wrote: > > On Thu, 2014-10-30 at 18:06 +0200, Or Gerlitz wrote: > >> Remove the code which goes through napi_gro_frags() on the RX path, > >> use only napi_gro_receive(). > > > Hmpff... napi_gro_frags() should be faster. > > Have you benchmarked this ? > > > yep we did, napi_gro_frags() was somehow better for single stream. Do > you think we need to do it the other way around, e.g converge to use > napi_gro_frags()? napi_gro_frags() is faster because the napi->skb is reused fast (not going through kfree_skb()/alloc_skb() for every fragment) -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists