From: Wei Wang <wei.w.wang@intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: jasowang@redhat.com, marcandre.lureau@gmail.com,
virtio-dev@lists.oasis-open.org, qemu-devel@nongnu.org,
stefanha@gmail.com, pbonzini@redhat.com, armbru@redhat.com,
jan.scheurich@ericsson.com
Subject: Re: [Qemu-devel] [virtio-dev] Re: [PATCH v2 1/2] virtio-net: enable configurable tx queue size
Date: Fri, 23 Jun 2017 08:46:02 +0800 [thread overview]
Message-ID: <594C64CA.5030703@intel.com> (raw)
In-Reply-To: <20170622170016-mutt-send-email-mst@kernel.org>
On 06/22/2017 10:00 PM, Michael S. Tsirkin wrote:
> On Sat, Jun 17, 2017 at 04:38:03PM +0800, Wei Wang wrote:
>> On 06/16/2017 10:31 PM, Michael S. Tsirkin wrote:
>>> On Fri, Jun 16, 2017 at 06:48:38PM +0800, 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 in total after translattion from
>>>> guest-physical address in the backend.
>>>>
>>>> Signed-off-by: Wei Wang <wei.w.wang@intel.com>
>>>> ---
>>>> hw/net/virtio-net.c | 46 ++++++++++++++++++++++++++++++++++--------
>>>> include/hw/virtio/virtio-net.h | 1 +
>>>> 2 files changed, 39 insertions(+), 8 deletions(-)
>>>>
>>>> diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c
>>>> index 7d091c9..e1a08fd 100644
>>>> --- a/hw/net/virtio-net.c
>>>> +++ b/hw/net/virtio-net.c
>>>> @@ -33,8 +33,11 @@
>>>> /* previously fixed value */
>>>> #define VIRTIO_NET_RX_QUEUE_DEFAULT_SIZE 256
>>>> +#define VIRTIO_NET_TX_QUEUE_DEFAULT_SIZE 256
>>>> +
>>>> /* for now, only allow larger queues; with virtio-1, guest can downsize */
>>>> #define VIRTIO_NET_RX_QUEUE_MIN_SIZE VIRTIO_NET_RX_QUEUE_DEFAULT_SIZE
>>>> +#define VIRTIO_NET_TX_QUEUE_MIN_SIZE VIRTIO_NET_TX_QUEUE_DEFAULT_SIZE
>>>> /*
>>>> * Calculate the number of bytes up to and including the given 'field' of
>>>> @@ -1491,18 +1494,33 @@ static void virtio_net_tx_bh(void *opaque)
>>>> static void virtio_net_add_queue(VirtIONet *n, int index)
>>>> {
>>>> VirtIODevice *vdev = VIRTIO_DEVICE(n);
>>>> + NetClientState *nc = qemu_get_queue(n->nic);
>>>> n->vqs[index].rx_vq = virtio_add_queue(vdev, n->net_conf.rx_queue_size,
>>>> virtio_net_handle_rx);
>>>> +
>>>> + /*
>>>> + * 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) {
>>>> + fprintf(stderr, "warning: %s: queue size %d not supported\n",
>>>> + __func__, n->net_conf.tx_queue_size);
>>>> + n->net_conf.tx_queue_size = VIRTIO_NET_TX_QUEUE_DEFAULT_SIZE;
>>>> + }
>>>> +
>>> Also, I suspect we can get here with no peer, and above will crash.
>>> It seems ugly to do this on each virtio_net_add_queue.
>>> How about moving this to realize?
>> The code has been re-arranged to make sure nc->peer is ready before
>> it's used, but I agree that it looks better to move the above to realize().
>>
>> Best,
>> Wei
> ping
>
> The issues left are minor, let's make progress and merge this asap
>
OK. I'll send out the new version soon.
Best,
Wei
prev parent reply other threads:[~2017-06-23 0:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 10:48 [Qemu-devel] [PATCH v2 1/2] virtio-net: enable configurable tx queue size Wei Wang
2017-06-16 10:48 ` [Qemu-devel] [PATCH v2 2/2] virtio-net: code cleanup Wei Wang
2017-06-16 14:19 ` [Qemu-devel] [PATCH v2 1/2] virtio-net: enable configurable tx queue size Michael S. Tsirkin
2017-06-16 14:31 ` Michael S. Tsirkin
2017-06-17 8:38 ` Wei Wang
2017-06-22 14:00 ` Michael S. Tsirkin
2017-06-23 0:46 ` Wei Wang [this message]
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=594C64CA.5030703@intel.com \
--to=wei.w.wang@intel.com \
--cc=armbru@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).