All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, mst@redhat.com
Cc: ehabkost@redhat.com, stefanha@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH] virtio-net: calculating proper msix vectors on init
Date: Tue, 9 Mar 2021 12:24:02 +0800	[thread overview]
Message-ID: <a1093267-332f-74f0-c9a0-ee543a2b8794@redhat.com> (raw)
In-Reply-To: <5a0806aa-af0b-2a41-c604-ede8dd49de31@redhat.com>


On 2021/3/8 6:06 下午, Philippe Mathieu-Daudé wrote:
> Hi Jason,
>
> On 3/8/21 6:30 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 pais + plus one config interrupt and control vq). We didn't
> Typo "pairs".
>
>> 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>
>> ---
>>   hw/core/machine.c          | 1 +
>>   hw/virtio/virtio-net-pci.c | 8 +++++++-
>>   2 files changed, 8 insertions(+), 1 deletion(-)
>>
>> diff --git a/hw/core/machine.c b/hw/core/machine.c
>> index 4386f57b5c..979133f8b7 100644
>> --- a/hw/core/machine.c
>> +++ b/hw/core/machine.c
>> @@ -39,6 +39,7 @@
>>   GlobalProperty hw_compat_5_2[] = {
>>       { "ICH9-LPC", "smm-compat", "on"},
>>       { "PIIX4_PM", "smm-compat", "on"},
>> +    { "virtio-net-pci", "vectors", "3"},
>>   };
>>   const size_t hw_compat_5_2_len = G_N_ELEMENTS(hw_compat_5_2);
>>   
>> diff --git a/hw/virtio/virtio-net-pci.c b/hw/virtio/virtio-net-pci.c
>> index 292d13d278..2894c46b66 100644
>> --- a/hw/virtio/virtio-net-pci.c
>> +++ b/hw/virtio/virtio-net-pci.c
>> @@ -41,7 +41,8 @@ struct VirtIONetPCI {
>>   static Property virtio_net_properties[] = {
>>       DEFINE_PROP_BIT("ioeventfd", VirtIOPCIProxy, flags,
>>                       VIRTIO_PCI_FLAG_USE_IOEVENTFD_BIT, true),
>> -    DEFINE_PROP_UINT32("vectors", VirtIOPCIProxy, nvectors, 3),
>> +    DEFINE_PROP_UINT32("vectors", VirtIOPCIProxy, nvectors,
>> +                       DEV_NVECTORS_UNSPECIFIED),
>>       DEFINE_PROP_END_OF_LIST(),
>>   };
>>   
>> @@ -50,6 +51,11 @@ static void virtio_net_pci_realize(VirtIOPCIProxy *vpci_dev, Error **errp)
>>       DeviceState *qdev = DEVICE(vpci_dev);
>>       VirtIONetPCI *dev = VIRTIO_NET_PCI(vpci_dev);
>>       DeviceState *vdev = DEVICE(&dev->vdev);
>> +    VirtIONet *net = VIRTIO_NET(vdev);
>> +
>> +    if (vpci_dev->nvectors == DEV_NVECTORS_UNSPECIFIED) {
>> +        vpci_dev->nvectors = 2 * MAX(net->nic_conf.peers.queues, 1) + 2;
> Please either document that magic '2':
>
>             vpci_dev->nvectors = 2 * MAX(net->nic_conf.peers.queues, 1)
>                                  + 1 /* Config interrupt */
>                                  + 1 /* Control vq */;
>
> Or add self-explicit definitions and use them in place.


Ok, V2 is sent.

Thanks


>
>> +    }
>>   
>>       virtio_net_set_netclient_name(&dev->vdev, qdev->id,
>>                                     object_get_typename(OBJECT(qdev)));
>>
>



  reply	other threads:[~2021-03-09  4:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-08  5:30 [PATCH] virtio-net: calculating proper msix vectors on init Jason Wang
2021-03-08 10:06 ` Philippe Mathieu-Daudé
2021-03-09  4:24   ` Jason Wang [this message]
2021-03-08 14:39 ` Stefan Hajnoczi

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=a1093267-332f-74f0-c9a0-ee543a2b8794@redhat.com \
    --to=jasowang@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=mst@redhat.com \
    --cc=philmd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.