From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: dev@dpdk.org, david.marchand@redhat.com, chenbox@nvidia.com
Subject: Re: [PATCH v3 0/2] vhost: add VDUSE reconnection support
Date: Tue, 24 Sep 2024 20:22:01 +0200 [thread overview]
Message-ID: <9eb8bde7-4bb2-4de2-9a0c-ec64aaaf7632@redhat.com> (raw)
In-Reply-To: <20240923195151.73527-1-maxime.coquelin@redhat.com>
On 9/23/24 21:51, Maxime Coquelin wrote:
> This series adds support for VDUSE reconnection.
>
> First patch introduces the reconnection file layout and
> track the virtqueues available index updates in the
> datapath and control queue.
>
> Second patch adds VDUSE reconnect intialization and some
> sanity checks to prevent incompatible reconnections.
>
> Changes in v3:
> ==============
> - Fixed missing avail index updates (David)
> - Fixed typos in commit message (David)
> - Applied R-by's
>
> Changes in v2:
> ==============
> - Added more sanity checks at reconnection
> - Improve versionning
> - Fix error loggin (Chenbo)
> - Clarify why offloading device start is required (Chenbo)
> - Change runtime path to <RUNPATH>/vduse instead of <RUNPATH>/dpdk/vduse
>
> Maxime Coquelin (2):
> vhost: add logging mechanism for reconnection
> vhost: add reconnection support to VDUSE
>
> lib/vhost/vduse.c | 308 +++++++++++++++++++++++++++++++-----
> lib/vhost/vhost.c | 2 +
> lib/vhost/vhost.h | 41 ++++-
> lib/vhost/vhost_user.c | 4 +
> lib/vhost/virtio_net.c | 8 +
> lib/vhost/virtio_net_ctrl.c | 2 +
> 6 files changed, 322 insertions(+), 43 deletions(-)
>
Applied to next-virtio/for-next-net
prev parent reply other threads:[~2024-09-24 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 19:51 Maxime Coquelin
2024-09-23 19:51 ` [PATCH v3 1/2] vhost: add logging mechanism for reconnection Maxime Coquelin
2024-09-23 19:51 ` [PATCH v3 2/2] vhost: add reconnection support to VDUSE Maxime Coquelin
2024-09-24 18:22 ` Maxime Coquelin [this message]
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=9eb8bde7-4bb2-4de2-9a0c-ec64aaaf7632@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=chenbox@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
/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).