netdev - Re: [PATCH net-next 0/4] Introduce NETIF_F_GRO

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20171205.143139.2139801110634773125.davem@davemloft.net>
Date:   Tue, 05 Dec 2017 14:31:39 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     michael.chan@...adcom.com
Cc:     netdev@...r.kernel.org
Subject: Re: [PATCH net-next 0/4] Introduce NETIF_F_GRO_HW

From: Michael Chan <michael.chan@...adcom.com>
Date: Mon,  4 Dec 2017 06:12:43 -0500

> Introduce NETIF_F_GRO_HW feature flag and convert drivers that support
> hardware GRO to use the flag.

So I think we should continue ahead with NETIF_F_GRO_HW.

LRO, even if it were in some way more appropriate, has so many stigmas
attached to it.  And if you look around the internet, articles say to
turn it off for this reason or that due to the information loss LRO
creates.

The only thing unresolved is how to manage the situation where a
bond or bridge has a mixture of LRO and GRO_HW devices attached,
and Michael said he would look into it.

Thanks.