From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Gal Pressman <gal@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
netdev@vger.kernel.org
Cc: Igor Russkikh <irusskikh@marvell.com>,
Boris Pismenny <borisp@nvidia.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
Tariq Toukan <tariqt@nvidia.com>,
Mark Bloch <mbloch@nvidia.com>,
David Ahern <dsahern@kernel.org>,
Simon Horman <horms@kernel.org>,
Alexander Duyck <alexanderduyck@fb.com>,
linux-rdma@vger.kernel.org, Gal Pressman <gal@nvidia.com>,
Dragos Tatulea <dtatulea@nvidia.com>
Subject: Re: [PATCH net-next 1/3] udp: gso: Use single MSS length in UDP header for GSO_PARTIAL
Date: Mon, 26 Jan 2026 12:53:31 -0500 [thread overview]
Message-ID: <willemdebruijn.kernel.218d53621fba7@gmail.com> (raw)
In-Reply-To: <20260125121649.778086-2-gal@nvidia.com>
Gal Pressman wrote:
> In GSO_PARTIAL segmentation, set the UDP length field to the single
> segment size (gso_size + UDP header) instead of the large MSS size.
> This provides hardware with a template length value for final
> segmentation, similar to how tunnel GSO_PARTIAL handles outer headers
> in UDP tunnels.
>
> This will remove the need to manually adjust the UDP header length in
> the drivers, as can be seen in subsequent patches.
>
> This was suggested by Alex in 2018:
> https://lore.kernel.org/netdev/CAKgT0UcdnUWgr3KQ=RnLKigokkiUuYefmL-ePpDvJOBNpKScFA@mail.gmail.com/
>
> Reviewed-by: Dragos Tatulea <dtatulea@nvidia.com>
> Signed-off-by: Gal Pressman <gal@nvidia.com>
Reviewed-by: Willem de Bruijn <willemb@google.com>
This only affects the udp header value when using GSO_PARTIAL, and
these are the only two drivers that adversize USO using GSO_PARTIAL.
> ---
> net/ipv4/udp_offload.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/net/ipv4/udp_offload.c b/net/ipv4/udp_offload.c
> index 19d0b5b09ffa..89e0b48b60ae 100644
> --- a/net/ipv4/udp_offload.c
> +++ b/net/ipv4/udp_offload.c
> @@ -483,11 +483,11 @@ struct sk_buff *__udp_gso_segment(struct sk_buff *gso_skb,
> struct sock *sk = gso_skb->sk;
> unsigned int sum_truesize = 0;
> struct sk_buff *segs, *seg;
> + __be16 newlen, msslen;
> struct udphdr *uh;
> unsigned int mss;
> bool copy_dtor;
> __sum16 check;
> - __be16 newlen;
> int ret = 0;
>
> mss = skb_shinfo(gso_skb)->gso_size;
> @@ -555,6 +555,8 @@ struct sk_buff *__udp_gso_segment(struct sk_buff *gso_skb,
> return segs;
> }
>
> + msslen = htons(sizeof(*uh) + mss);
> +
> /* GSO partial and frag_list segmentation only requires splitting
> * the frame into an MSS multiple and possibly a remainder, both
> * cases return a GSO skb. So update the mss now.
> @@ -584,7 +586,7 @@ struct sk_buff *__udp_gso_segment(struct sk_buff *gso_skb,
> if (!seg->next)
> break;
>
> - uh->len = newlen;
> + uh->len = msslen;
> uh->check = check;
>
> if (seg->ip_summed == CHECKSUM_PARTIAL)
> --
> 2.40.1
>
next prev parent reply other threads:[~2026-01-26 19:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-25 12:16 [PATCH net-next 0/3] Single MSS length in UDP GSO_PARTIAL Gal Pressman
2026-01-25 12:16 ` [PATCH net-next 1/3] udp: gso: Use single MSS length in UDP header for GSO_PARTIAL Gal Pressman
2026-01-26 17:53 ` Willem de Bruijn [this message]
2026-02-03 12:20 ` Alice Mikityanska
2026-02-03 13:51 ` Gal Pressman
2026-02-04 12:47 ` Alice Mikityanska
2026-01-25 12:16 ` [PATCH net-next 2/3] net/mlx5e: Remove redundant UDP length adjustment with GSO_PARTIAL Gal Pressman
2026-01-27 7:50 ` Tariq Toukan
2026-01-25 12:16 ` [PATCH net-next 3/3] net: aquantia: " Gal Pressman
2026-01-28 1:40 ` [PATCH net-next 0/3] Single MSS length in UDP GSO_PARTIAL patchwork-bot+netdevbpf
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=willemdebruijn.kernel.218d53621fba7@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=alexanderduyck@fb.com \
--cc=andrew+netdev@lunn.ch \
--cc=borisp@nvidia.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=irusskikh@marvell.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
/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