From: "Zhu, Lingshan" <lingshan.zhu@intel.com>
To: Jason Wang <jasowang@redhat.com>, mst@redhat.com
Cc: virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH 0/2] vDPA/ifcvf: enable multiqueue and control vq
Date: Thu, 19 Aug 2021 14:49:46 +0800 [thread overview]
Message-ID: <9e6f6cb0-eaed-9d83-c297-3a89f5cc9efd@intel.com> (raw)
In-Reply-To: <e3ec8ed7-84ac-73cc-0b74-4de1bb6c0030@redhat.com>
On 8/19/2021 12:11 PM, Jason Wang wrote:
>
> 在 2021/8/18 下午5:57, Zhu Lingshan 写道:
>> This series enables multi-queue and control vq features
>> for ifcvf.
>>
>> These patches are based on my previous vDPA/ifcvf management link
>> implementation series:
>> https://lore.kernel.org/kvm/20210812032454.24486-2-lingshan.zhu@intel.com/T/
>>
>>
>> Thanks!
>>
>> Zhu Lingshan (2):
>> vDPA/ifcvf: detect and use the onboard number of queues directly
>> vDPA/ifcvf: enable multiqueue and control vq
>>
>> drivers/vdpa/ifcvf/ifcvf_base.c | 8 +++++---
>> drivers/vdpa/ifcvf/ifcvf_base.h | 19 ++++---------------
>> drivers/vdpa/ifcvf/ifcvf_main.c | 32 +++++++++++++++-----------------
>> 3 files changed, 24 insertions(+), 35 deletions(-)
>>
>
> Patch looks good.
>
> I wonder the compatibility. E.g does it work on the qemu master
> without cvq support? (mq=off or not specified)
Hi Jason,
Yes, it works with qemu master. When no cvq/mq support, only one queue
pair shown.
Thanks,
Zhu Lingshan
>
> Thanks
>
next prev parent reply other threads:[~2021-08-19 6:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 9:57 [PATCH 0/2] vDPA/ifcvf: enable multiqueue and control vq Zhu Lingshan
2021-08-18 9:57 ` [PATCH 1/2] vDPA/ifcvf: detect and use the onboard number of queues directly Zhu Lingshan
2021-08-19 4:09 ` Jason Wang
2021-08-18 9:57 ` [PATCH 2/2] vDPA/ifcvf: enable multiqueue and control vq Zhu Lingshan
2021-08-19 4:09 ` Jason Wang
2021-08-19 4:11 ` [PATCH 0/2] " Jason Wang
2021-08-19 6:49 ` Zhu, Lingshan [this message]
2021-08-19 7:15 ` Jason Wang
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=9e6f6cb0-eaed-9d83-c297-3a89f5cc9efd@intel.com \
--to=lingshan.zhu@intel.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--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).