From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Jakub Sitnicki <jakub@cloudflare.com>, netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Willem de Bruijn <willemb@google.com>,
kernel-team@cloudflare.com
Subject: Re: [PATCH net 0/2] Lift UDP_SEGMENT restriction for egress via device w/o csum offload
Date: Sun, 23 Jun 2024 04:18:35 -0400 [thread overview]
Message-ID: <6677da5b3c52e_334d34294dd@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <20240622-linux-udpgso-v1-0-d2344157ab2a@cloudflare.com>
Jakub Sitnicki wrote:
> This is a follow-up to an earlier question [1] if we can make UDP GSO work with
> any egress device, even those with no checksum offload capability. That's the
> default setup for TUN/TAP.
>
> I leave it to the maintainers to decide if it qualifies as a fix. We plan to
> backport it to our v6.6 either way, hence the submission to -net.
>
> [1] https://lore.kernel.org/netdev/87jzqsld6q.fsf@cloudflare.com/
Agreed with the change to allow UDP_SEGMENT to work regardless of
device capabilities.
In my opinion this is a new feature with sufficient risk of unintended
side effects to be net-next material.
Maybe worth recording in patch 1 the reason for the original check:
that UDP_SEGMENT with software checksumming in the GSO stack may be
a regression vs copy_and_checksum in the send syscall.
>
> Signed-off-by: Jakub Sitnicki <jakub@cloudflare.com>
> ---
> Jakub Sitnicki (2):
> udp: Allow GSO transmit from devices with no checksum offload
> selftests/net: Add test coverage for UDP GSO software fallback
>
> net/ipv4/udp.c | 3 +--
> net/ipv4/udp_offload.c | 8 +++++++
> net/ipv6/udp.c | 3 +--
> tools/testing/selftests/net/udpgso.c | 15 +++++++++---
> tools/testing/selftests/net/udpgso.sh | 43 +++++++++++++++++++++++++++++++++++
> 5 files changed, 65 insertions(+), 7 deletions(-)
>
next prev parent reply other threads:[~2024-06-23 8:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-22 16:14 [PATCH net 0/2] Lift UDP_SEGMENT restriction for egress via device w/o csum offload Jakub Sitnicki
2024-06-22 16:14 ` [PATCH net 1/2] udp: Allow GSO transmit from devices with no checksum offload Jakub Sitnicki
2024-06-22 16:14 ` [PATCH net 2/2] selftests/net: Add test coverage for UDP GSO software fallback Jakub Sitnicki
2024-06-23 2:27 ` Jakub Kicinski
2024-06-24 10:20 ` Jakub Sitnicki
2024-06-23 8:18 ` Willem de Bruijn [this message]
2024-06-24 11:29 ` [PATCH net 0/2] Lift UDP_SEGMENT restriction for egress via device w/o csum offload Jakub Sitnicki
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=6677da5b3c52e_334d34294dd@willemb.c.googlers.com.notmuch \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jakub@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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;
as well as URLs for NNTP newsgroup(s).