diff options
author | Michael Chan <michael.chan@broadcom.com> | 2017-12-16 03:09:40 -0500 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2017-12-19 10:38:36 -0500 |
commit | fb1f5f79ae96331a0201b4080d34f3bc3b5c0b1d (patch) | |
tree | cf5acb01f5d79f0f140b0b100d3ba46bef881fed /net/dns_resolver | |
parent | 398b841e4ad69a822f615442b5ea4ca767330a3b (diff) | |
download | op-kernel-dev-fb1f5f79ae96331a0201b4080d34f3bc3b5c0b1d.zip op-kernel-dev-fb1f5f79ae96331a0201b4080d34f3bc3b5c0b1d.tar.gz |
net: Introduce NETIF_F_GRO_HW.
Introduce NETIF_F_GRO_HW feature flag for NICs that support hardware
GRO. With this flag, we can now independently turn on or off hardware
GRO when GRO is on. Previously, drivers were using NETIF_F_GRO to
control hardware GRO and so it cannot be independently turned on or
off without affecting GRO.
Hardware GRO (just like GRO) guarantees that packets can be re-segmented
by TSO/GSO to reconstruct the original packet stream. Logically,
GRO_HW should depend on GRO since it a subset, but we will let
individual drivers enforce this dependency as they see fit.
Since NETIF_F_GRO is not propagated between upper and lower devices,
NETIF_F_GRO_HW should follow suit since it is a subset of GRO. In other
words, a lower device can independent have GRO/GRO_HW enabled or disabled
and no feature propagation is required. This will preserve the current
GRO behavior. This can be changed later if we decide to propagate GRO/
GRO_HW/RXCSUM from upper to lower devices.
Cc: Ariel Elior <Ariel.Elior@cavium.com>
Cc: everest-linux-l2@cavium.com
Signed-off-by: Michael Chan <michael.chan@broadcom.com>
Acked-by: Alexander Duyck <alexander.h.duyck@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/dns_resolver')
0 files changed, 0 insertions, 0 deletions