From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Jason Wang <jasowang@redhat.com>,
ehabkost@redhat.com, marcel.apfelbaum@gmail.com, mst@redhat.com
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [PATCH V2] virtio-net: calculating proper msix vectors on init
Date: Tue, 9 Mar 2021 09:46:59 +0100 [thread overview]
Message-ID: <67f4d3b9-ed1f-f2c2-1e9f-d9558f1eff36@redhat.com> (raw)
In-Reply-To: <20210309042314.45817-1-jasowang@redhat.com>
On 3/9/21 5:23 AM, Jason Wang wrote:
> Currently, the default msix vectors for virtio-net-pci is 3 which is
> obvious not suitable for multiqueue guest, so we depends on the user
> or management tools to pass a correct vectors parameter. In fact, we
> can simplifying this by calculating the number of vectors on realize.
>
> Consider we have N queues, the number of vectors needed is 2*N + 2
> (#queue pairs + plus one config interrupt and control vq). We didn't
> check whether or not host support control vq because it was added
> unconditionally by qemu to avoid breaking legacy guests such as Minix.
>
> Signed-off-by: Jason Wang <jasowang@redhat.com>
> ---
> Changes since v1:
> - Fix typo in the commit log
> - Explain the magic number during vectors calculation
> ---
> hw/core/machine.c | 1 +
> hw/virtio/virtio-net-pci.c | 10 +++++++++-
> 2 files changed, 10 insertions(+), 1 deletion(-)
(the patch had Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>)
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2021-03-09 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 4:23 [PATCH V2] virtio-net: calculating proper msix vectors on init Jason Wang
2021-03-09 8:46 ` Philippe Mathieu-Daudé [this message]
2021-03-09 9:18 ` Stefan Hajnoczi
2021-03-09 11:13 ` Stefano Garzarella
2021-03-12 5:47 ` 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=67f4d3b9-ed1f-f2c2-1e9f-d9558f1eff36@redhat.com \
--to=philmd@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jasowang@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).