qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefano Garzarella <sgarzare@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: lulu@redhat.com, mst@redhat.com, qemu-devel@nongnu.org,
	gdawar@xilinx.com, eperezma@redhat.com, lingshan.zhu@intel.com,
	elic@nvidia.com
Subject: Re: [PATCH V4 03/10] vhost-vdpa: prepare for the multiqueue support
Date: Mon, 18 Oct 2021 17:44:23 +0200	[thread overview]
Message-ID: <20211018154423.uc3ehhrfvmxd3nry@steredhat> (raw)
In-Reply-To: <20211011042829.4159-4-jasowang@redhat.com>

On Mon, Oct 11, 2021 at 12:28:22PM +0800, Jason Wang wrote:
>Unlike vhost-kernel, vhost-vdpa adapts a single device multiqueue
>model. So we need to simply use virtqueue index as the vhost virtqueue
>index. This is a must for multiqueue to work for vhost-vdpa.
>
>Signed-off-by: Jason Wang <jasowang@redhat.com>
>Message-Id: <20210907090322.1756-4-jasowang@redhat.com>
>Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
>Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
>---
> hw/virtio/vhost-vdpa.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/hw/virtio/vhost-vdpa.c b/hw/virtio/vhost-vdpa.c
>index edac4017da..8587d30918 100644
>--- a/hw/virtio/vhost-vdpa.c
>+++ b/hw/virtio/vhost-vdpa.c
>@@ -504,8 +504,8 @@ static int vhost_vdpa_get_vq_index(struct vhost_dev *dev, int idx)
> {
>     assert(idx >= dev->vq_index && idx < dev->vq_index + dev->nvqs);

Should we also change this assert?

Thanks,
Stefano

>
>-    trace_vhost_vdpa_get_vq_index(dev, idx, idx - dev->vq_index);
>-    return idx - dev->vq_index;
>+    trace_vhost_vdpa_get_vq_index(dev, idx, idx);
>+    return idx;
> }
>
> static int vhost_vdpa_set_vring_ready(struct vhost_dev *dev)
>-- 
>2.25.1
>
>



  reply	other threads:[~2021-10-18 15:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-11  4:28 [PATCH V4 00/10] vhost-vDPA multiqueue Jason Wang
2021-10-11  4:28 ` [PATCH V4 01/10] vhost-vdpa: open device fd in net_init_vhost_vdpa() Jason Wang
2021-10-11  4:28 ` [PATCH V4 02/10] vhost-vdpa: classify one time request Jason Wang
2021-10-11  4:28 ` [PATCH V4 03/10] vhost-vdpa: prepare for the multiqueue support Jason Wang
2021-10-18 15:44   ` Stefano Garzarella [this message]
2021-10-20  2:50     ` Jason Wang
2021-10-11  4:28 ` [PATCH V4 04/10] vhost-vdpa: let net_vhost_vdpa_init() returns NetClientState * Jason Wang
2021-10-11  4:28 ` [PATCH V4 05/10] net: introduce control client Jason Wang
2021-10-11  4:28 ` [PATCH V4 06/10] vhost-net: control virtqueue support Jason Wang
2021-10-11  4:28 ` [PATCH V4 07/10] virtio-net: use "queue_pairs" instead of "queues" when possible Jason Wang
2021-10-11  4:28 ` [PATCH V4 08/10] vhost: record the last virtqueue index for the virtio device Jason Wang
2021-10-11  4:28 ` [PATCH V4 09/10] virtio-net: vhost control virtqueue support Jason Wang
2021-10-11  4:28 ` [PATCH V4 10/10] vhost-vdpa: multiqueue support Jason Wang
2021-10-19  7:21 ` [PATCH V4 00/10] vhost-vDPA multiqueue Michael S. Tsirkin
2021-10-19  7:24   ` Jason Wang
2021-10-19 10:44     ` Michael S. Tsirkin
2021-10-19 11:17       ` Michael S. Tsirkin

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=20211018154423.uc3ehhrfvmxd3nry@steredhat \
    --to=sgarzare@redhat.com \
    --cc=elic@nvidia.com \
    --cc=eperezma@redhat.com \
    --cc=gdawar@xilinx.com \
    --cc=jasowang@redhat.com \
    --cc=lingshan.zhu@intel.com \
    --cc=lulu@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.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).