qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* Inconsistent virtio-net-pci MSI vector count
@ 2021-03-03 10:53 Stefan Hajnoczi
  2021-03-03 13:08 ` Jason Wang
  2021-03-03 16:08 ` Michael S. Tsirkin
  0 siblings, 2 replies; 5+ messages in thread
From: Stefan Hajnoczi @ 2021-03-03 10:53 UTC (permalink / raw)
  To: jasowang; +Cc: qemu-devel, Michael S. Tsirkin

[-- Attachment #1: Type: text/plain, Size: 931 bytes --]

Hi Jason,
I stumbled across something strange with virtio-net multi-queue today.
It doesn't seem to be a bug in practice, just an inconsistency. Here are
the details in case you think something needs to be changed:

libvirt uses the vectors = 2 * N + 2 formula from
https://www.linux-kvm.org/page/Multiqueue to calculate the number of PCI
MSI vectors, where N is the number of rx/tx queue pairs.

QEMU's virtio-net-pci device has 3 MSI vectors by default. This is
inconsistent with the formula that libvirt uses (should be 4 instead of
3).

Luckily, the Linux virtio_net.ko driver does not configure a callback
function for the control virtqueue. Therefore it can still use MSI with
only 3 vectors (config, rx, tx) instead of 4 (config, rx, tx, ctrl).

But other driver implementations might need the ctrl vq vector and would
not have enough MSI vectors.

Perhaps new QEMU machine types should set vectors to 4 by default?

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2021-03-03 17:10 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-03-03 10:53 Inconsistent virtio-net-pci MSI vector count Stefan Hajnoczi
2021-03-03 13:08 ` Jason Wang
2021-03-03 16:12   ` Michael S. Tsirkin
2021-03-03 17:09     ` Stefan Hajnoczi
2021-03-03 16:08 ` Michael S. Tsirkin

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).