From: Paolo Abeni <pabeni@redhat.com>
To: Jason Wang <jasowang@redhat.com>, Willem de Bruijn <willemb@google.com>
Cc: virtio-comment@lists.linux.dev, maxime.coquelin@redhat.com,
Eelco Chaudron <echaudro@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>,
kshankar@marvell.com
Subject: Re: [PATCH v9 1/2] virtio-net: define UDP tunnel segmentation offload feature
Date: Mon, 28 Oct 2024 13:08:30 +0100 [thread overview]
Message-ID: <a036a534-722d-49cd-bdb2-cf60aadd249f@redhat.com> (raw)
In-Reply-To: <CACGkMEs4xb=xEH2RwQYZFEP9WGdwT2jOSERmpzTto+PQuxgcwg@mail.gmail.com>
On 10/28/24 04:27, Jason Wang wrote:
> As the topic becomes more complicated, I wonder if we can do something
> easier, that is focusing on the one checksum offload first. And I
> would like to check the current Linux behaviour first for non-GSO UDP
> tunnel:
>
> 1) For TX, as you've mentioned, the csum_start/offset has already
> pointed to the inner header (but is this the innermost?)
> 2) For RX, what header would csum_start/offset points (considering we
> have nested tunnels)
>
> I'm asking to make sure our proposal doesn't conflict with the
> existing implementation.
In Linux, csum_start/offset, both for rx and tx, points to the innermost
_offloaded_ header.
On RX, since GSO partial does not apply, such innermost offloaded header
correspond the outermost/only header (when no tunnels are configured) or
the 2nd outermost, when tunnels are configured and GRO-ed.
On TX, via GSO partial and local csum offload, the csum_start can, in
theory point to an header with an header with an arbitrary high level,
but currently no driver/tx path allow for GSO partial with more than 1
encapsulation level (may change in the future).
The proposed specification change in v9 for NEED_CSUM matches the above.
Since reaching an agreement WRT DATA_VALID handling looks problematic,
would you consider a virtual meeting to discuss the topic?
Thanks,
Paolo
p.s. to be clear, with 'you' I include both Jason and Willem.
next prev parent reply other threads:[~2024-10-28 12:08 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 8:13 [PATCH v9 0/2] virtio-net: define UDP tunnel offload Paolo Abeni
2024-10-04 8:13 ` [PATCH v9 1/2] virtio-net: define UDP tunnel segmentation offload feature Paolo Abeni
2024-10-09 7:18 ` Jason Wang
2024-10-09 8:37 ` Paolo Abeni
2024-10-10 3:17 ` Jason Wang
2024-10-10 7:40 ` Paolo Abeni
2024-10-11 2:08 ` Jason Wang
2024-10-11 7:50 ` Paolo Abeni
2024-10-14 7:20 ` Paolo Abeni
2024-10-17 6:47 ` Jason Wang
2024-10-17 15:34 ` Paolo Abeni
2024-10-18 4:26 ` Jason Wang
2024-10-18 10:10 ` Paolo Abeni
2024-10-20 22:28 ` Willem de Bruijn
2024-10-21 15:47 ` Paolo Abeni
2024-10-22 7:54 ` Jason Wang
2024-10-23 20:57 ` Willem de Bruijn
2024-10-25 8:41 ` Jason Wang
2024-10-21 6:54 ` Jason Wang
2024-10-21 16:27 ` Paolo Abeni
2024-10-22 7:42 ` Jason Wang
2024-10-22 16:56 ` Paolo Abeni
2024-10-25 8:28 ` Jason Wang
2024-10-25 11:50 ` Paolo Abeni
2024-10-25 13:28 ` Willem de Bruijn
2024-10-25 14:35 ` Paolo Abeni
2024-10-25 15:47 ` Willem de Bruijn
2024-10-28 3:27 ` Jason Wang
2024-10-28 12:08 ` Paolo Abeni [this message]
2024-10-28 12:26 ` Willem de Bruijn
2024-10-28 14:23 ` Paolo Abeni
2024-10-29 7:32 ` Jason Wang
2024-10-04 8:13 ` [PATCH v9 2/2] virtio-net: define UDP tunnel checksum " Paolo Abeni
2024-10-09 7:18 ` Jason Wang
2024-10-09 9:39 ` Paolo Abeni
2024-10-10 4:22 ` Jason Wang
2024-10-04 16:53 ` [PATCH v9 0/2] virtio-net: define UDP tunnel offload Paolo Abeni
2024-10-09 7:24 ` Jason Wang
2024-10-09 8:08 ` Paolo Abeni
2024-10-10 2:29 ` Jason Wang
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=a036a534-722d-49cd-bdb2-cf60aadd249f@redhat.com \
--to=pabeni@redhat.com \
--cc=echaudro@redhat.com \
--cc=jasowang@redhat.com \
--cc=kshankar@marvell.com \
--cc=maxime.coquelin@redhat.com \
--cc=sgarzare@redhat.com \
--cc=virtio-comment@lists.linux.dev \
--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