[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240425150432.44142-1-nbd@nbd.name>
Date: Thu, 25 Apr 2024 17:04:23 +0200
From: Felix Fietkau <nbd@....name>
To: netdev@...r.kernel.org
Cc: willemdebruijn.kernel@...il.com,
pabeni@...hat.com,
edumazet@...gle.com
Subject: [PATCH v2 net-next 0/5] Add TCP fraglist GRO support
When forwarding TCP after GRO, software segmentation is very expensive,
especially when the checksum needs to be recalculated.
One case where that's currently unavoidable is when routing packets over
PPPoE. Performance improves significantly when using fraglist GRO
implemented in the same way as for UDP.
When NETIF_F_GRO_FRAGLIST is enabled, perform a lookup for an established
socket in the same netns as the receiving device. While this may not
cover all relevant use cases in multi-netns configurations, it should be
good enough for most configurations that need this.
Here's a measurement of running 2 TCP streams through a MediaTek MT7622
device (2-core Cortex-A53), which runs NAT with flow offload enabled from
one ethernet port to PPPoE on another ethernet port + cake qdisc set to
1Gbps.
rx-gro-list off: 630 Mbit/s, CPU 35% idle
rx-gro-list on: 770 Mbit/s, CPU 40% idle
Changes since v1:
- revert bogus tcp flags overwrite on segmentation
- fix kbuild issue with !CONFIG_IPV6
- only perform socket lookup for the first skb in the GRO train
Changes since RFC:
- split up patches
- handle TCP flags mutations
Felix Fietkau (5):
net: move skb_gro_receive_list from udp to core
net: add support for segmenting TCP fraglist GSO packets
net: add code for TCP fraglist GRO
net: create tcp_gro_lookup helper function
net: add heuristic for enabling TCP fraglist GRO
include/net/gro.h | 1 +
include/net/tcp.h | 1 +
net/core/gro.c | 27 ++++++
net/ipv4/tcp_offload.c | 180 +++++++++++++++++++++++++++++++++++----
net/ipv4/udp_offload.c | 27 ------
net/ipv6/tcpv6_offload.c | 63 ++++++++++++++
6 files changed, 256 insertions(+), 43 deletions(-)
--
2.44.0
Powered by blists - more mailing lists