From: Jason Wang <jasowang@redhat.com>
To: mst@redhat.com, jasowang@redhat.com, eperezma@redhat.com
Cc: kvm@vger.kernel.org, virtualization@lists.linux.dev,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
jonah.palmer@oracle.com
Subject: [PATCH net-next V2 0/3] in order support for vhost-net
Date: Mon, 14 Jul 2025 16:47:52 +0800 [thread overview]
Message-ID: <20250714084755.11921-1-jasowang@redhat.com> (raw)
Hi all,
This series implements VIRTIO_F_IN_ORDER support for vhost-net. This
feature is designed to improve the performance of the virtio ring by
optimizing descriptor processing.
Benchmarks show a notable improvement. Please see patch 3 for details.
Changes since V1:
- add a new patch to fail early when vhost_add_used() fails
- drop unused parameters of vhost_add_used_ooo()
- conisty nheads for vhost_add_used_in_order()
- typo fixes and other tweaks
Thanks
Jason Wang (3):
vhost: fail early when __vhost_add_used() fails
vhost: basic in order support
vhost_net: basic in_order support
drivers/vhost/net.c | 88 +++++++++++++++++++++---------
drivers/vhost/vhost.c | 123 ++++++++++++++++++++++++++++++++++--------
drivers/vhost/vhost.h | 8 ++-
3 files changed, 171 insertions(+), 48 deletions(-)
--
2.39.5
next reply other threads:[~2025-07-14 8:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 8:47 Jason Wang [this message]
2025-07-14 8:47 ` [PATCH net-next V2 1/3] vhost: fail early when __vhost_add_used() fails Jason Wang
2025-07-14 8:47 ` [PATCH net-next V2 2/3] vhost: basic in order support Jason Wang
2025-07-28 14:26 ` Eugenio Perez Martin
2025-07-14 8:47 ` [PATCH net-next V2 3/3] vhost_net: basic in_order support Jason Wang
2025-07-16 1:12 ` [PATCH net-next V2 0/3] in order support for vhost-net Lei Yang
2025-07-17 0:04 ` Jakub Kicinski
2025-07-17 2:03 ` Jason Wang
2025-07-17 5:54 ` Michael S. Tsirkin
2025-07-17 6:01 ` Jason Wang
2025-07-17 6:31 ` Michael S. Tsirkin
2025-07-17 13:52 ` Paolo Abeni
2025-07-18 2:04 ` Jason Wang
2025-07-18 9:19 ` Paolo Abeni
2025-07-18 9:29 ` Michael S. Tsirkin
2025-07-18 9:44 ` 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=20250714084755.11921-1-jasowang@redhat.com \
--to=jasowang@redhat.com \
--cc=eperezma@redhat.com \
--cc=jonah.palmer@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux.dev \
/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