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: <20180410163216.GB3661@localhost.localdomain> Date: Tue, 10 Apr 2018 13:32:16 -0300 From: Marcelo Ricardo Leitner <marcelo.leitner@...il.com> To: Wenhua Shi <march511@...il.com> Cc: David Miller <davem@...emloft.net>, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] make net_gso_ok return false when gso_type is zero(invalid) On Sun, Apr 08, 2018 at 08:41:21PM +0200, Wenhua Shi wrote: > 2018-04-08 18:51 GMT+02:00 David Miller <davem@...emloft.net>: > > > > From: Wenhua Shi <march511@...il.com> > > Date: Fri, 6 Apr 2018 03:43:39 +0200 > > > > > Signed-off-by: Wenhua Shi <march511@...il.com> > > > > This precondition should be made impossible instead of having to do > > an extra check everywhere that this helper is invoked, many of which > > are in fast paths. > > I believe the precondition you said is quite true. In my situation, I > have to disable GSO for some packet and I notice that it leads to a > worse performance (slower than 1Mbps, was almost 800Mbps). > > Here's the hook I use on debian 9.4, kernel version 4.9: There is quite a distance between 4.9 and net/net-next. Did you test on a more recent kernel too? Note that TCP stack now works with GSO being always on. 0a6b2a1dc2a2 ("tcp: switch to GSO being always on")
Powered by blists - more mailing lists