From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, mlureau@redhat.com,
zhengxiang9@huawei.com, lersek@redhat.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/4] vhost-user: fix multiple queue specification
Date: Tue, 16 Jan 2018 13:35:24 +0100 [thread overview]
Message-ID: <481b4c1f-c0da-0614-e553-50dca87d7b4c@redhat.com> (raw)
In-Reply-To: <20180116045637-mutt-send-email-mst@kernel.org>
On 01/16/2018 04:00 AM, Michael S. Tsirkin wrote:
> On Fri, Jan 12, 2018 at 03:56:55PM +0100, Maxime Coquelin wrote:
>> The number of queues supported by the slave is queried with
>> message VHOST_USER_GET_QUEUE_NUM, not with message
>> VHOST_USER_GET_PROTOCOL_FEATURES.
>>
>> Also, looking at master and slave implemntations, the payload
>> returned by the slave is the number of queue pairs supported
>> by the slave, not the number of queues.
>
> virtio doesn't have a concept of queue pairs. virtio net does
> have a concept of a tx/rx pair for purposes of steering.
Ok, thanks for the clarification. I will have a look at how vhost-user
SCSI implements it.
> Would this be a slave bug then?
If I'm not mistaken, the bug is in QEMU:
VHOST_USER_GET_QUEUE_NUM is stored in (struct vhost_dev).max_queues.
vhost_net_get_max_queues() returns (struct vhost_dev).max_queues.
And vhost_user_start() from net/vhost-user.c calls
vhost_net_get_max_queues() to get the max number of tx/rx pairs.
If we want to fix QEMU, I think we will need a new flag for
compatibility with older/current backends that assume it represent a
queue pair.
> I've applied the 1st chunk for now.
Thanks.
>> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
>> ---
>> docs/interop/vhost-user.txt | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/docs/interop/vhost-user.txt b/docs/interop/vhost-user.txt
>> index d49444e037..8a14191a1e 100644
>> --- a/docs/interop/vhost-user.txt
>> +++ b/docs/interop/vhost-user.txt
>> @@ -214,8 +214,8 @@ Multiple queue is treated as a protocol extension, hence the slave has to
>> implement protocol features first. The multiple queues feature is supported
>> only when the protocol feature VHOST_USER_PROTOCOL_F_MQ (bit 0) is set.
>>
>> -The max number of queues the slave supports can be queried with message
>> -VHOST_USER_GET_PROTOCOL_FEATURES. Master should stop when the number of
>> +The max number of queue pairs the slave supports can be queried with message
>> +VHOST_USER_GET_QUEUE_NUM. Master should stop when the number of
>> requested queues is bigger than that.
>>
>> As all queues share one connection, the master uses a unique index for each
>> @@ -537,7 +537,7 @@ Master message types
>> Master payload: N/A
>> Slave payload: u64
>>
>> - Query how many queues the backend supports. This request should be
>> + Query how many queue pairs the backend supports. This request should be
>> sent only when VHOST_USER_PROTOCOL_F_MQ is set in queried protocol
>> features by VHOST_USER_GET_PROTOCOL_FEATURES.
>>
>> --
>> 2.14.3
next prev parent reply other threads:[~2018-01-16 12:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 14:56 [Qemu-devel] [PATCH 0/4] vhost-user: notify backend with number of queues setup Maxime Coquelin
2018-01-12 14:56 ` [Qemu-devel] [PATCH 1/4] vhost-user: fix multiple queue specification Maxime Coquelin
2018-01-16 3:00 ` Michael S. Tsirkin
2018-01-16 12:35 ` Maxime Coquelin [this message]
2018-01-12 14:56 ` [Qemu-devel] [PATCH 2/4] vhost-user: specify and implement VHOST_USER_SET_QUEUE_NUM request Maxime Coquelin
2018-01-16 3:05 ` Michael S. Tsirkin
2018-01-16 14:56 ` Maxime Coquelin
2018-01-12 14:56 ` [Qemu-devel] [PATCH 3/4] vhost-net: add vhost_net_set_queue_num helper Maxime Coquelin
2018-01-12 14:56 ` [Qemu-devel] [PATCH 4/4] virtio-net: notify backend with number of queue pairs setup Maxime Coquelin
2018-01-16 3:07 ` Michael S. Tsirkin
2018-01-16 14:16 ` Maxime Coquelin
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=481b4c1f-c0da-0614-e553-50dca87d7b4c@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=lersek@redhat.com \
--cc=mlureau@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhengxiang9@huawei.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).