From: David Marchand <david.marchand@redhat.com>
To: maxime.coquelin@redhat.com, dev@dpdk.org
Subject: [PATCH 0/5] Drop vhost async (DMA-accelerated) datapath
Date: Wed, 26 Aug 2026 16:02:01 +0200 [thread overview]
Message-ID: <20260826140206.1099433-1-david.marchand@redhat.com> (raw)
In-Reply-To: <20260723153111.3943368-1-david.marchand@redhat.com>
The integration of this feature in OVS has been postponed following
feedback how the current API forced the complexity on the application
side. There is no contributor working on making those changes.
The feature has no other identified opensource consumer.
On the other hand, this feature has been left unattended for some years
now while the "normal" datapath is actively maintained.
It is highly likely the async datapath code, which never underwent a
stabilisation phase, is riddled with bugs.
Given the craziness around finding security bugs with AI,
and since the vhost library is a good target, I propose to drop
this feature and reduce the library attack surface.
There is one complication with the vhost_crypto and some external
applications that seemed to rely on the async flag to track and populate
guest pages, so a new flag replacing async is added by this series.
--
David Marchand
Changes since RFC:
- maintained guest pages population in a new flag (vhost_crypto/SPDK),
- removed remaining helpers which had sync_ in their names,
David Marchand (5):
vhost: decouple guest pages population from async datapath
examples/vhost: stop using async datapath
vhost: drop async datapath
vhost: rename packed layout helpers for batches
vhost: simplify some descriptor handling
doc/guides/prog_guide/vhost_lib.rst | 152 +-
doc/guides/rel_notes/release_26_11.rst | 20 +
examples/vhost/Makefile | 2 -
examples/vhost/main.c | 436 +--
examples/vhost/main.h | 21 +-
examples/vhost/meson.build | 2 -
examples/vhost_crypto/Makefile | 1 -
examples/vhost_crypto/main.c | 2 +-
examples/vhost_crypto/meson.build | 1 -
lib/vhost/meson.build | 3 +-
lib/vhost/rte_vhost.h | 2 +-
lib/vhost/rte_vhost_async.h | 293 ---
lib/vhost/socket.c | 20 +-
lib/vhost/vhost.c | 434 ---
lib/vhost/vhost.h | 116 +-
lib/vhost/vhost_user.c | 115 +-
lib/vhost/virtio_net.c | 3343 +++++-------------------
17 files changed, 736 insertions(+), 4227 deletions(-)
delete mode 100644 lib/vhost/rte_vhost_async.h
--
2.54.0
next prev parent reply other threads:[~2026-08-26 14:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 15:31 [RFC 0/3] Drop vhost async (DMA-accelerated) datapath David Marchand
2026-07-23 15:31 ` [RFC 1/3] examples: stop using vhost async datapath David Marchand
2026-08-25 11:39 ` David Marchand
2026-07-23 15:31 ` [RFC 2/3] vhost: refuse " David Marchand
2026-07-23 15:31 ` [RFC 3/3] vhost: drop " David Marchand
2026-08-18 9:10 ` [RFC 0/3] Drop vhost async (DMA-accelerated) datapath Maxime Coquelin
2026-08-26 14:02 ` David Marchand [this message]
2026-08-26 14:02 ` [PATCH 1/5] vhost: decouple guest pages population from async datapath David Marchand
2026-08-26 14:02 ` [PATCH 2/5] examples/vhost: stop using " David Marchand
2026-08-26 14:02 ` [PATCH 3/5] vhost: drop " David Marchand
2026-08-26 14:02 ` [PATCH 4/5] vhost: rename packed layout helpers for batches David Marchand
2026-08-26 14:02 ` [PATCH 5/5] vhost: simplify some descriptor handling David Marchand
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=20260826140206.1099433-1-david.marchand@redhat.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@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