From: Wei Wang <wei.w.wang@intel.com>
To: Jason Wang <jasowang@redhat.com>,
mst@redhat.com, eblake@redhat.com,
virtio-dev@lists.oasis-open.org, qemu-devel@nongnu.org
Cc: stefanha@gmail.com, armbru@redhat.com,
jan.scheurich@ericsson.com, marcandre.lureau@gmail.com,
pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 1/2] virtio-net: enable configurable tx queue size
Date: Mon, 26 Jun 2017 12:55:04 +0800 [thread overview]
Message-ID: <595093A8.1080902@intel.com> (raw)
In-Reply-To: <9c3402b1-961d-b953-ca6c-188b03ed756b@redhat.com>
On 06/26/2017 11:18 AM, Jason Wang wrote:
>
> On 2017年06月23日 10:32, Wei Wang wrote:
>> This patch enables the virtio-net tx queue size to be configurable
>> between 256 (the default queue size) and 1024 by the user when the
>> vhost-user backend is used.
>>
>> Currently, the maximum tx queue size for other backends is 512 due
>> to the following limitations:
>> - QEMU backend: the QEMU backend implementation in some cases may
>> send 1024+1 iovs to writev.
>> - Vhost_net backend: there are possibilities that the guest sends
>> a vring_desc of memory which corsses a MemoryRegion thereby
>> generating more than 1024 iovs after translattion from guest-physical
>> address in the backend.
>>
>> Signed-off-by: Wei Wang <wei.w.wang@intel.com>
>> ---
>> hw/net/virtio-net.c | 45
>> +++++++++++++++++++++++++++++++++---------
>> include/hw/virtio/virtio-net.h | 1 +
>> 2 files changed, 37 insertions(+), 9 deletions(-)
>>
>> diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c
>> index 91eddaf..d13ca60 100644
>> --- a/hw/net/virtio-net.c
>> +++ b/hw/net/virtio-net.c
>> @@ -34,8 +34,11 @@
>> /* previously fixed value */
>> #define VIRTIO_NET_RX_QUEUE_DEFAULT_SIZE 256
>> +
>> + /*
>> + * Currently, backends other than vhost-user don't support 1024
>> queue
>> + * size.
>> + */
>> + if (n->net_conf.tx_queue_size == VIRTQUEUE_MAX_SIZE &&
>> + nc->peer->info->type != NET_CLIENT_DRIVER_VHOST_USER) {
>> + n->net_conf.tx_queue_size = VIRTIO_NET_TX_QUEUE_DEFAULT_SIZE;
>
> Do we really want assume all vhost-user backend support 1024 queue size?
>
Do you know any vhost-user backend implementation that doesn't support
1024 tx queue size?
>> + }
>> +
>> + for (i = 0; i < n->max_queues; i++) {
>> + virtio_net_add_queue(n, i);
>> + }
>
> Any reason to move virtio_net_add_queue() here?
>
Please check the whole init steps. It was moved here (after qemu_new_nic())
to make sure nc->peer is not NULL.
Best,
Wei
next prev parent reply other threads:[~2017-06-26 4:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 2:32 [Qemu-devel] [PATCH v3 1/2] virtio-net: enable configurable tx queue size Wei Wang
2017-06-23 2:32 ` [Qemu-devel] [PATCH v3 2/2] virtio-net: code cleanup Wei Wang
2017-06-26 3:18 ` [Qemu-devel] [PATCH v3 1/2] virtio-net: enable configurable tx queue size Jason Wang
2017-06-26 4:55 ` Wei Wang [this message]
2017-06-26 8:05 ` [Qemu-devel] [virtio-dev] " Jason Wang
2017-06-26 10:34 ` Wei Wang
2017-06-26 21:21 ` Michael S. Tsirkin
2017-06-27 1:06 ` Wei Wang
2017-06-27 1:51 ` Michael S. Tsirkin
2017-06-27 2:19 ` Jason Wang
2017-06-27 5:22 ` Wang, Wei W
2017-06-27 1:51 ` [Qemu-devel] " Eric Blake
2017-06-27 5:24 ` Wang, Wei W
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=595093A8.1080902@intel.com \
--to=wei.w.wang@intel.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=jan.scheurich@ericsson.com \
--cc=jasowang@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=virtio-dev@lists.oasis-open.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 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).