From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: virtio-comment@lists.linux.dev, Jason Wang <jasowang@redhat.com>,
maxime.coquelin@redhat.com, Eelco Chaudron <echaudro@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>,
Willem de Bruijn <willemb@google.com>,
kshankar@marvell.com
Subject: Re: [PATCH v11 0/4] virtio-net: define UDP tunnel offload
Date: Tue, 14 Jan 2025 10:16:53 -0500 [thread overview]
Message-ID: <20250114101553-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <175a0b29-5901-4393-9390-64a018bec260@redhat.com>
On Tue, Jan 14, 2025 at 04:04:35PM +0100, Paolo Abeni wrote:
> On 11/27/24 10:48 AM, Paolo Abeni wrote:
> > On 11/27/24 10:36, Paolo Abeni wrote:
> >> UDP tunnel usage is ubiquitous in container deployment, and the ability
> >> to offload UDP encapsulated GSO traffic impacts greatly the performances
> >> and the CPU utilization of such use cases.
> >>
> >> This series includes:
> >> - clarifications on the current semantic of NEEDS_CSUM offload
> >> (patch 1) and DATA_VALID offload (patch 2) to make later changes easier
> >> to follow,
> >> - new features definition to handle both UDP tunnel segmentation
> >> offload (patch 3).
> >> - new features definition to handle UDP tunnel outer checksum offload
> >> (patch 4).
> >>
> >> A PoC implementation is available here:
> >>
> >> https://github.com/pabeni/linux-devel/commits/virtio_tunnel_gso_v10/
> >> https://github.com/pabeni/qemu/tree/virtio_tunnel_gso_v9
> >>
> >> Note that both implementations has not been updated since the previous
> >> iteration, since there are no additional functional changes in v11.
> >>
> >> Changes from v10:
> >> - added patch 2
> >> - clarified only a single encapsulation level is supported (patch 3)
> >> - s/TCP or UDP GSO packets/GSO packets/ (patch 3)
> >> - 'to the outer UDP pseudo header' -> 'to the outer UDP pseudo header
> >> checksum' (patch 4)
> >> https://lore.kernel.org/virtio-comment/cover.1731084277.git.pabeni@redhat.com/
>
> I understand all the points under discussion have been addressed. I'm
> wondering the next steps are and what I could do to move things forward.
>
> Thanks,
>
> Paolo
See
https://github.com/oasis-tcs/virtio-spec?tab=readme-ov-file#use-of-github-issues
for the process to get a change merged once there is concensus.
--
MST
next prev parent reply other threads:[~2025-01-14 15:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 9:36 [PATCH v11 0/4] virtio-net: define UDP tunnel offload Paolo Abeni
2024-11-27 9:36 ` [PATCH v11 1/4] virtio-net: clarify NEEDS_CSUM semantic for GSO packats Paolo Abeni
2024-11-28 3:00 ` Jason Wang
2025-01-19 7:56 ` Parav Pandit
2024-11-27 9:36 ` [PATCH v11 2/4] virtio-net: clarify DATA_VALID semantic for encap protos Paolo Abeni
2024-11-28 3:01 ` Jason Wang
2025-01-19 7:57 ` Parav Pandit
2024-11-27 9:36 ` [PATCH v11 3/4] virtio-net: define UDP tunnel segmentation offload feature Paolo Abeni
2024-11-28 3:01 ` Jason Wang
2025-01-19 8:06 ` Parav Pandit
2025-01-20 8:44 ` Paolo Abeni
2025-01-20 8:57 ` Parav Pandit
2025-01-20 9:03 ` Cornelia Huck
2025-01-20 11:32 ` Parav Pandit
2025-01-20 12:20 ` Cornelia Huck
2025-01-20 14:19 ` Parav Pandit
2025-01-20 14:50 ` Cornelia Huck
2025-01-21 18:40 ` Paolo Abeni
2025-01-21 19:38 ` Parav Pandit
2025-01-22 14:43 ` Paolo Abeni
2025-01-26 6:24 ` Parav Pandit
2024-11-27 9:36 ` [PATCH v11 4/4] virtio-net: define UDP tunnel checksum " Paolo Abeni
2024-11-28 3:01 ` Jason Wang
2024-11-27 9:48 ` [PATCH v11 0/4] virtio-net: define UDP tunnel offload Paolo Abeni
2025-01-14 15:04 ` Paolo Abeni
2025-01-14 15:16 ` Michael S. Tsirkin [this message]
2025-01-14 15:57 ` 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=20250114101553-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=echaudro@redhat.com \
--cc=jasowang@redhat.com \
--cc=kshankar@marvell.com \
--cc=maxime.coquelin@redhat.com \
--cc=pabeni@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.