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: <20101003.003129.193711520.davem@davemloft.net> Date: Sun, 03 Oct 2010 00:31:29 -0700 (PDT) From: David Miller <davem@...emloft.net> To: sysoleg@...dex.ru Cc: richard@...ce.co.nz, netdev@...r.kernel.org Subject: Re: To GRO or not to GRO... From: "\"Oleg A. Arkhangelsky\"" <sysoleg@...dex.ru> Date: Sun, 03 Oct 2010 11:18:46 +0400 > > > 03.10.2010, 03:17, "Richard Scobie" <richard@...ce.co.nz>: > >> In the README for ixgbe-2.1.4, is says: >> >> " Disable GRO when routing/bridging >> --------------------------------- >> Due to a known kernel issue, GRO must be turned off when >> routing/bridging. >> GRO can be turned off via ethtool." >> > > This information is true for LRO, not GRO. Right. > I believe that this appeared when ixgbe was converted from LRO > to GRO and all occurrences of LRO was blindly replaced by GRO > everywhere. Someome please submit a patch to fix this, thanks. -- 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