DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev@dpdk.org, chenbox@nvidia.com
Subject: Re: [PATCH v2 1/2] vhost: add logging mechanism for reconnection
Date: Mon, 23 Sep 2024 11:42:49 -0400	[thread overview]
Message-ID: <CAJFAV8wGMGNSGO4tKuHhKsPQ2kgnY_mR9iMtCZA9b+9zQ2d39A@mail.gmail.com> (raw)
In-Reply-To: <20240920150921.994434-2-maxime.coquelin@redhat.com>

On Fri, Sep 20, 2024 at 11:09 AM Maxime Coquelin
<maxime.coquelin@redhat.com> wrote:
>
> This patch introduces a way for backend to keep track
> of the needed information to be able to reconnect without
> frontend cooperation.
>
> It will be used for VDUSE, which does not provide interface
> for the backend to save and later recover local virtqueues
> metadata needed to reconnect.
>
> Vhost-user support could also be added for improved packed
> ring reconnection support.
>
> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>

vq->last_avail_idx gets updated in other places and I suspect we are
missing some calls to vhost_virtqueue_reconnect_log_split/packed.
I spotted:
- lib/vhost/vhost.c: rte_vhost_set_vring_base()
- lib/vhost/vhost_user.c:  translate_ring_addresses(),
vhost_user_set_vring_base().

The rest lgtm.


-- 
David Marchand


  parent reply	other threads:[~2024-09-23 15:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-20 15:09 [PATCH v2 0/2] vhost: add VDUSE reconnection support Maxime Coquelin
2024-09-20 15:09 ` [PATCH v2 1/2] vhost: add logging mechanism for reconnection Maxime Coquelin
2024-09-23  7:12   ` Chenbo Xia
2024-09-23 15:42   ` David Marchand [this message]
2024-09-23 19:46     ` Maxime Coquelin
2024-09-20 15:09 ` [PATCH v2 2/2] vhost: add reconnection support to VDUSE Maxime Coquelin
2024-09-23  7:13   ` Chenbo Xia
2024-09-23 16:43   ` 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=CAJFAV8wGMGNSGO4tKuHhKsPQ2kgnY_mR9iMtCZA9b+9zQ2d39A@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=chenbox@nvidia.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;
as well as URLs for NNTP newsgroup(s).