From: Paolo Abeni <pabeni@redhat.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Simon Horman <horms@kernel.org>,
Neal Cardwell <ncardwell@google.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
David Ahern <dsahern@kernel.org>
Subject: [RFC PATCH 0/2] net: gro: avoid touching transport header
Date: Fri, 5 Dec 2025 15:03:29 +0100 [thread overview]
Message-ID: <cover.1764943231.git.pabeni@redhat.com> (raw)
This series is basically a pre-req for GRO support for double UDP
encapsulation:
https://lore.kernel.org/netdev/cover.1764056123.git.pabeni@redhat.com/
that otherwise would requiring explicitly disabling gro on the outer
geneve device.
I *think* it should also help plain TCP GRO performances, even if don't
have a very high speed, full zero-copy, big TCP testbed handy to
actually prove it - see patch 1 for the gory details.
Paolo Abeni (2):
net: gro: avoid relaying on skb->transport_header at receive time
net: gro: set the transport header later
include/net/gro.h | 26 ++++++++++++++++++++++++++
include/net/tcp.h | 3 ++-
net/ipv4/af_inet.c | 2 +-
net/ipv4/tcp_offload.c | 16 +++++++++-------
net/ipv4/udp_offload.c | 8 ++++++--
net/ipv6/ip6_offload.c | 3 +--
net/ipv6/tcpv6_offload.c | 2 +-
7 files changed, 46 insertions(+), 14 deletions(-)
--
2.52.0
next reply other threads:[~2025-12-05 14:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 14:03 Paolo Abeni [this message]
2025-12-05 14:03 ` [RFC PATCH 1/2] net: gro: avoid relaying on skb->transport_header at receive time Paolo Abeni
2025-12-05 14:37 ` Eric Dumazet
2025-12-05 15:22 ` Paolo Abeni
2025-12-05 15:36 ` Eric Dumazet
2025-12-06 21:26 ` Willem de Bruijn
2025-12-05 14:03 ` [RFC PATCH 2/2] net: gro: set the transport header later Paolo Abeni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1764943231.git.pabeni@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).