From: Paolo Abeni <pabeni@redhat.com>
To: Jason Wang <jasowang@redhat.com>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>,
Cornelia Huck <cohuck@redhat.com>, Eric Blake <eblake@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Akihiko Odaki <odaki@rsg.ci.i.u-tokyo.ac.jp>
Subject: Re: [PATCH v5 00/13] virtio: introduce support for GSO over UDP tunnel
Date: Mon, 1 Sep 2025 08:44:46 +0200 [thread overview]
Message-ID: <8c41ea67-c5a3-4f16-85a2-cc4876f09995@redhat.com> (raw)
In-Reply-To: <CACGkMEvOmgGyqv5-FGDAgyDrY9TpssEDtpNp07ro2oamg_7r1w@mail.gmail.com>
On 9/1/25 4:47 AM, Jason Wang wrote:
> On Thu, Aug 28, 2025 at 9:47 AM Akihiko Odaki
> <odaki@rsg.ci.i.u-tokyo.ac.jp> wrote:
>>
>> On 2025/08/13 19:28, Paolo Abeni wrote:
>>> Some virtualized deployments use UDP tunnel pervasively and are impacted
>>> negatively by the lack of GSO support for such kind of traffic in the
>>> virtual NIC driver.
>>>
>>> The virtio_net specification recently introduced support for GSO over
>>> UDP tunnel, and the kernel side of the implementation has been merged
>>> into the net-next tree; this series updates the virtio implementation to
>>> support such a feature.
>>>
>>> Currently the qemu virtio support limits the feature space to 64 bits,
>>> while the virtio specification allows for a larger number of features.
>>> Specifically the GSO-over-UDP-tunnel-related virtio features use bits
>>> 65-69; the larger part of this series (patches 4-12) actually deals with
>>> extending the features space.
>>>
>>> The extended features are carried by fixed size uint64_t arrays,
>>> bringing the current maximum features number to 128.
>>>
>>> The patches use some syntactic sugar to try to minimize the otherwise
>>> very large code churn. Specifically the extended features are boundled
>>> in an union with 'legacy' features definition, allowing no changes in
>>> the virtio devices not needing the extended features set.
>>>
>>> The actual offload implementation is in patches 13 and 14 and boils down
>>> to propagating the new offload to the tun devices and the vhost backend.
>>>
>>> Patch 1 is a small pre-req refactor that ideally could enter the
>>> tree separately; it's presented here in the same series to help
>>> reviewers more easily getting the full picture, patch 2 updates to
>>> linux headers update script to deal with annotations recently introduce
>>> in the kernel and patch 3 is a needed linux headers update.
>>>
>>> Tested with basic stream transfer with all the possible permutations of
>>> host kernel/qemu/guest kernel with/without GSO over UDP tunnel support,
>>> vs snapshots creation and restore and vs migration.
>>>
>>> The new features are disabled by default to avoid compatibilty issues.
>>> They could be enabled after that hw_compat_10_1 will be added, together
>>> with the related compatiblity entries.
>>>
>>> Based-on: 9d71108d7de139dd4f4e6efe6837cabb32bf5616.1755078918.git.pabeni@redhat.com
>>
>> Now everything looks good to me. For the whole series:
>>
>> Reviewed-by: Akihiko Odaki <odaki@rsg.ci.i.u-tokyo.ac.jp>
>>
>> Regards,
>> Akihiko Odaki
>>
>
> Acked-by: Jason Wang <jasowang@redhat.com>
Thank you for the feedback. I guess this series will go through
Micheal's tree, am I correct?
Also I suspect/fear it could need rebasing due to some other patches
being applied meanwhile, please LMK if a repost is needed, thanks!
Paolo
next prev parent reply other threads:[~2025-09-01 6:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 10:28 [PATCH v5 00/13] virtio: introduce support for GSO over UDP tunnel Paolo Abeni
2025-08-13 10:28 ` [PATCH v5 01/13] linux-headers: deal with counted_by annotation Paolo Abeni
2025-08-13 10:28 ` [PATCH v5 02/13] linux-headers: Update to Linux v6.17-rc1 Paolo Abeni
2025-08-13 10:28 ` [PATCH v5 03/13] virtio: introduce extended features type Paolo Abeni
2025-08-13 10:28 ` [PATCH v5 04/13] virtio: serialize extended features state Paolo Abeni
2025-08-13 10:28 ` [PATCH v5 05/13] virtio: add support for negotiating extended features Paolo Abeni
2025-08-13 10:28 ` [PATCH v5 06/13] virtio-pci: implement support for " Paolo Abeni
2025-08-13 10:28 ` [PATCH v5 07/13] vhost: add support for negotiating " Paolo Abeni
2025-08-13 10:28 ` [PATCH v5 08/13] qmp: update virtio features map to support " Paolo Abeni
2025-08-30 8:05 ` Markus Armbruster
2025-08-13 10:28 ` [PATCH v5 09/13] vhost-backend: implement extended features support Paolo Abeni
2025-08-13 10:28 ` [PATCH v5 10/13] vhost-net: " Paolo Abeni
2025-08-13 10:28 ` [PATCH v5 11/13] virtio-net: " Paolo Abeni
2025-08-13 10:28 ` [PATCH v5 12/13] net: implement tunnel probing Paolo Abeni
2025-08-13 10:28 ` [PATCH v5 13/13] net: implement UDP tunnel features offloading Paolo Abeni
2025-08-14 3:26 ` [PATCH v5 00/13] virtio: introduce support for GSO over UDP tunnel Lei Yang
2025-08-22 7:45 ` Paolo Abeni
2025-08-28 1:47 ` Akihiko Odaki
2025-09-01 2:47 ` Jason Wang
2025-09-01 6:44 ` Paolo Abeni [this message]
2025-09-02 9:08 ` Jason Wang
2025-09-02 9:51 ` Michael S. Tsirkin
2025-09-01 14:54 ` Stefano Garzarella
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=8c41ea67-c5a3-4f16-85a2-cc4876f09995@redhat.com \
--to=pabeni@redhat.com \
--cc=armbru@redhat.com \
--cc=cohuck@redhat.com \
--cc=eblake@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=odaki@rsg.ci.i.u-tokyo.ac.jp \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.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).