From: Laurent Vivier <lvivier@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v2 2/6] vhost-user: Enable multiqueue
Date: Wed, 26 Nov 2025 09:04:30 +0100 [thread overview]
Message-ID: <e74b7494-90d9-4b02-b3cd-795e9c91559e@redhat.com> (raw)
In-Reply-To: <aSZj-SRmZKEmSuaq@zatzit>
On 11/26/25 03:20, David Gibson wrote:
> On Fri, Nov 21, 2025 at 05:58:58PM +0100, Laurent Vivier wrote:
>> Add the --max-queues parameter to specify the maximum number of
>> queue
>
> Nit: you updated the option to be --max-qpairs, which I think is good,
> but now the commit message is out of date.
>
>
> One other query: what makes it "max qpairs" rather than just "qpairs"
> - are there (now or in planned work) circumstances where you'd end up
> with less qpairs than specified here?
In fact, the number of qpairs is negociated by the guest. If you start passt with
max-qpairs=16 but QEMU with queues=4, it will only use 4 qpairs. If you start QEMU with
queues=17, it will fail.
Perhaps we can remove the parameter and rely only on the hardcoded one (32 virtqueues = 16
qpairs)? I can add "--mq" parameter instead to enable multiqueue?
>
>> pairs supported in vhost-user mode. This enables multi-queue support
>> by allowing configuration of up to 16 queue pairs (32 virtqueues).
>>
>> For the moment, only the first RX queue is used, the TX queue is
>> selected by the guest kernel.
>
> IIUC, with this patch (but not the ones after) things will break if
> the guest uses a qpair other than 0, right? AFAICT vu_kick_cb() isn't
> updated so will ignore anything on the other qpairs.
No, I think it should work. For the TX part (from guest) we add all the kick_fd to the
epollfd, so all the TX queues are managed. But we we use only RX queue 0, that is not what
is expected by the guest kernel as we should use the same queue pair but I think kernel
will process them anyway.
Thanks,
Laurent
next prev parent reply other threads:[~2025-11-26 8:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 16:58 [PATCH v2 0/6] vhost-user: Add multiqueue support Laurent Vivier
2025-11-21 16:58 ` [PATCH v2 1/6] tap: Remove pool parameter from tap4_handler() and tap6_handler() Laurent Vivier
2025-11-21 16:58 ` [PATCH v2 2/6] vhost-user: Enable multiqueue Laurent Vivier
2025-11-26 2:20 ` David Gibson
2025-11-26 8:04 ` Laurent Vivier [this message]
2025-11-21 16:58 ` [PATCH v2 3/6] vhost-user: Add queue pair parameter throughout the network stack Laurent Vivier
2025-11-26 2:35 ` David Gibson
2025-11-21 16:59 ` [PATCH v2 4/6] tap: Add queue pair parameter throughout the packet processing path Laurent Vivier
2025-11-26 3:16 ` David Gibson
2025-11-21 16:59 ` [PATCH v2 5/6] flow: Add queue pair tracking to flow management Laurent Vivier
2025-11-26 3:41 ` David Gibson
2025-11-27 9:17 ` Laurent Vivier
2025-11-28 0:53 ` David Gibson
2025-11-21 16:59 ` [PATCH v2 6/6] test: Add multiqueue support to vhost-user test infrastructure Laurent Vivier
2025-11-26 3:45 ` David Gibson
2025-11-27 9:20 ` Laurent Vivier
2025-11-28 0:54 ` David Gibson
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=e74b7494-90d9-4b02-b3cd-795e9c91559e@redhat.com \
--to=lvivier@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).