virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Dragos Tatulea <dtatulea@nvidia.com>
Cc: "eperezma@redhat.com" <eperezma@redhat.com>,
	"mst@redhat.com" <mst@redhat.com>,
	"virtualization@lists.linux-foundation.org"
	<virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH RFC v2 0/3] vdpa: dedicated descriptor table group
Date: Tue, 12 Sep 2023 12:25:33 +0800	[thread overview]
Message-ID: <CACGkMEsCuzzBLiREiCRAnGXRY6K2UN58skNW3KPHh7UE5p6Jpw@mail.gmail.com> (raw)
In-Reply-To: <a9516f2b76d66f5292358b4509a854ebd57fb090.camel@nvidia.com>

On Mon, Sep 11, 2023 at 3:06 PM Dragos Tatulea <dtatulea@nvidia.com> wrote:
>
> Hi Jason,
>
> On Mon, 2023-09-11 at 14:43 +0800, Jason Wang wrote:
> > On Sat, Sep 9, 2023 at 4:45 PM Si-Wei Liu <si-wei.liu@oracle.com> wrote:
> > >
> > > Following patchset introduces dedicated group for descriptor table to
> > > reduce live migration downtime when passthrough VQ is being switched
> > > to shadow VQ. This RFC v2 is sent to incorporate the early feedback
> > > from reviewers on the uAPI and driver API part of changes, the
> > > associated driver patch set consuming ths API will come around
> > > soon along with formal submission of this series.
> > >
> > > Some initial performance data will be gathered using the real
> > > hardware device with mlx5_vdpa. The target goal of this series is to
> > > reduce the SVQ switching overhead to less than 300ms on a ~100GB
> > > guest with 2 non-mq vhost-vdpa devices. The reduction in the downtime
> > > is thanks to avoiding the full remap in the switching.
> > >
> > > The plan of the intended driver implementation is to use a dedicated
> > > group (specifically, 2 in below table) to host the descriptor tables
> > > for data vqs, different from where buffer addresses are contained (in
> > > group 0 as below). cvq does not have to allocate dedicated group for
> > > descriptor table, so its buffers and descriptor table would always
> > > belong to the same group (1 in table below).
> > >
> > >
> > >               |  data vq | ctrl vq
> > > ==============+==========+===========
> > > vq_group      |    0     |    1
> > > vq_desc_group |    2     |    1
> > >
> > >
> > > ---
> > >
> > > Si-Wei Liu (3):
> > >   vdpa: introduce dedicated descriptor group for virtqueue
> > >   vhost-vdpa: introduce descriptor group backend feature
> > >   vhost-vdpa: uAPI to get dedicated descriptor group id
> >
> > Looks good to me but I'd expect example implementations in the parent.
> >
> We (Si-Wei and I) will send a non-RFC series with the mlx5_vdpa implementation
> as soon as the submission window opens.
>
> Can we add your Acked-by for these core patches?

Yes.

Thanks

>
> Thanks,
> Dragos

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

      reply	other threads:[~2023-09-12  4:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-09  8:42 [PATCH RFC v2 0/3] vdpa: dedicated descriptor table group Si-Wei Liu
2023-09-09  8:42 ` [PATCH RFC v2 1/3] vdpa: introduce dedicated descriptor group for virtqueue Si-Wei Liu
2023-09-09  8:42 ` [PATCH RFC v2 2/3] vhost-vdpa: introduce descriptor group backend feature Si-Wei Liu
2023-09-09  8:42 ` [PATCH RFC v2 3/3] vhost-vdpa: uAPI to get dedicated descriptor group id Si-Wei Liu
2023-09-11  6:43 ` [PATCH RFC v2 0/3] vdpa: dedicated descriptor table group Jason Wang
2023-09-11  7:06   ` Dragos Tatulea via Virtualization
2023-09-12  4:25     ` Jason Wang [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=CACGkMEsCuzzBLiREiCRAnGXRY6K2UN58skNW3KPHh7UE5p6Jpw@mail.gmail.com \
    --to=jasowang@redhat.com \
    --cc=dtatulea@nvidia.com \
    --cc=eperezma@redhat.com \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.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).