summaryrefslogtreecommitdiffstats
path: root/drivers/net/ethernet/ibm/ehea/ehea_main.c
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2021-04-11 16:39:28 -0700
committerDavid S. Miller <davem@davemloft.net>2021-04-11 16:39:28 -0700
commit23cfa4d4aa9fa634e43edd7f92cde4f050b4f2db (patch)
tree155c5d55bcb73a63e71dcd8ca96807de13ac61bd /drivers/net/ethernet/ibm/ehea/ehea_main.c
parent7dc85b599ae17fb705ffae1b7321ace4b3056aeb (diff)
parent1c3cadbe02420e6c85251c416a78a16f17761231 (diff)
downloadlinux-23cfa4d4aa9fa634e43edd7f92cde4f050b4f2db.tar.bz2
Merge branch 'veth-gro'
Paolo Abeni says: ==================== veth: allow GRO even without XDP This series allows the user-space to enable GRO/NAPI on a veth device even without attaching an XDP program. It does not change the default veth behavior (no NAPI, no GRO), except that the GRO feature bit on top of this series will be effectively off by default on veth devices. Note that currently the GRO bit is on by default, but GRO never takes place in absence of XDP. On top of this series, setting the GRO feature bit enables NAPI and allows the GRO to take place. The TSO features on the peer device are preserved. The main goal is improving UDP forwarding performances for containers in a typical virtual network setup: (container) veth -> veth peer -> bridge/ovs -> vxlan -> NIC Enabling the NAPI threaded mode, GRO the NETIF_F_GRO_UDP_FWD feature on the veth peer improves the UDP stream performance with not void netfilter configuration by 2x factor with no measurable overhead for TCP traffic: some heuristic ensures that TCP will not go through the additional NAPI/GRO layer. Some self-tests are added to check the expected behavior in the default configuration, with XDP and with plain GRO enabled. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/ethernet/ibm/ehea/ehea_main.c')
0 files changed, 0 insertions, 0 deletions