From: Jason Wang <jasowang@redhat.com>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>,
"aliguori@amazon.com" <aliguori@amazon.com>,
"mst@redhat.com" <mst@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH V2] virtio-net: calculate proper msix vectors on init
Date: Tue, 04 Mar 2014 15:41:27 +0800 [thread overview]
Message-ID: <531583A7.60901@redhat.com> (raw)
In-Reply-To: <33183CC9F5247A488A2544077AF19020815D41F8@SZXEMA503-MBS.china.huawei.com>
On 03/04/2014 11:26 AM, Gonglei (Arei) wrote:
>> -----Original Message-----
>> From: qemu-devel-bounces+arei.gonglei=huawei.com@nongnu.org
>> [mailto:qemu-devel-bounces+arei.gonglei=huawei.com@nongnu.org] On
>> Behalf Of Jason Wang
>> Sent: Friday, February 21, 2014 5:05 PM
>> To: aliguori@amazon.com; mst@redhat.com; qemu-devel@nongnu.org
>> Cc: Paolo Bonzini; Jason Wang
>> Subject: [Qemu-devel] [PATCH V2] virtio-net: calculate proper msix vectors on
>> init
>>
>> 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 calculate the number of vectors on init.
>>
>> Consider we have N queues, the number of vectors needed is 2*N + 2
>> (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.
>>
>> Cc: Paolo Bonzini <pbonzini@redhat.com>
>> Cc: Michael S. Tsirkin <mst@redhat.com>
>> Signed-off-by: Jason Wang <jasowang@redhat.com>
>> ---
>> hw/virtio/virtio-pci.c | 8 +++++++-
>> 1 file changed, 7 insertions(+), 1 deletion(-)
>>
>> diff --git a/hw/virtio/virtio-pci.c b/hw/virtio/virtio-pci.c
>> index 7b91841..3b3b0e2 100644
>> --- a/hw/virtio/virtio-pci.c
>> +++ b/hw/virtio/virtio-pci.c
>> @@ -1416,7 +1416,8 @@ static const TypeInfo virtio_serial_pci_info = {
>> static Property virtio_net_properties[] = {
>> DEFINE_PROP_BIT("ioeventfd", VirtIOPCIProxy, flags,
>> VIRTIO_PCI_FLAG_USE_IOEVENTFD_BIT, false),
>> - DEFINE_PROP_UINT32("vectors", VirtIOPCIProxy, nvectors, 3),
>> + DEFINE_PROP_UINT32("vectors", VirtIOPCIProxy, nvectors,
>> + DEV_NVECTORS_UNSPECIFIED),
>> DEFINE_VIRTIO_NET_FEATURES(VirtIOPCIProxy, host_features),
>> DEFINE_NIC_PROPERTIES(VirtIONetPCI, vdev.nic_conf),
>> DEFINE_VIRTIO_NET_PROPERTIES(VirtIONetPCI, vdev.net_conf),
>> @@ -1428,6 +1429,11 @@ static int virtio_net_pci_init(VirtIOPCIProxy
>> *vpci_dev)
>> DeviceState *qdev = DEVICE(vpci_dev);
>> VirtIONetPCI *dev = VIRTIO_NET_PCI(vpci_dev);
>> DeviceState *vdev = DEVICE(&dev->vdev);
>> + VirtIONet *net = VIRTIO_NET(&dev->vdev);
>> +
>> + if (vpci_dev->nvectors == DEV_NVECTORS_UNSPECIFIED) {
>> + vpci_dev->nvectors = 2 * MAX(net->nic_conf.queues, 1) + 2;
>> + }
>>
>> virtio_net_set_config_size(&dev->vdev, vpci_dev->host_features);
>> virtio_net_set_netclient_name(&dev->vdev, qdev->id,
>> --
>> 1.8.3.2
>>
> Good catch.
>
> Reviewed-by: Gonglei <arei.gonglei@huawei.com>
>
>
> Best regards,
> -Gonglei
>
Hi Gonglei:
Thanks for the reviewing. Looks like this patch has a bug which will
break the migration if "vectors=" is not specified.
Will post a new version.
next prev parent reply other threads:[~2014-03-04 7:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 9:05 [Qemu-devel] [PATCH V2] virtio-net: calculate proper msix vectors on init Jason Wang
2014-03-04 3:26 ` Gonglei (Arei)
2014-03-04 7:34 ` Jason Wang
2014-03-04 7:41 ` Jason Wang [this message]
2014-03-04 11:18 ` Gonglei
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=531583A7.60901@redhat.com \
--to=jasowang@redhat.com \
--cc=aliguori@amazon.com \
--cc=arei.gonglei@huawei.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.