From: Wei Wang <wei.w.wang@intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: jasowang@redhat.com, eblake@redhat.com,
virtio-dev@lists.oasis-open.org, qemu-devel@nongnu.org,
armbru@redhat.com, stefanha@gmail.com,
marcandre.lureau@gmail.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [virtio-dev] Re: [PATCH v4] virtio-net: enable configurable tx queue size
Date: Tue, 04 Jul 2017 19:03:51 +0800 [thread overview]
Message-ID: <595B7617.4060203@intel.com> (raw)
In-Reply-To: <20170703220017-mutt-send-email-mst@kernel.org>
On 07/04/2017 03:18 AM, Michael S. Tsirkin wrote:
> On Wed, Jun 28, 2017 at 10:37:59AM +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 crosses a MemoryRegion thereby
>> generating more than 1024 iovs after translation from guest-physical
>> address in the backend.
>>
>> Signed-off-by: Wei Wang <wei.w.wang@intel.com>
> I was going to apply this, but run into a host of issues:
>
> This segfaults:
> $ ./x86_64-softmmu/qemu-system-x86_64 -device virtio-net,tx_queue_size=1024
> Segmentation fault (core dumped)
>
> I tried to tweak this code a bit to avoid the crash, and I run into a further issue:
> $ ./x86_64-softmmu/qemu-system-x86_64 -device virtio-net,tx_queue_size=1024
> Bad ram offset aa49002
> Aborted (core dumped)
>
> the second issue is especially concerning.
>
AFAIK, all the virtio-net backends require "-netdev". I'm wondering if there
is any case that virtio-net can work without a "-netdev" created in QEMU?
If not, would it be better if we just stop the device creation at the
beginning of
virtio_net_device_realize() if "-netdev" is not given (i.e.
!n->nic_conf.peers.ncs[0])?
Best,
Wei
next prev parent reply other threads:[~2017-07-04 11:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 2:37 [Qemu-devel] [PATCH v4] virtio-net: enable configurable tx queue size Wei Wang
2017-07-03 19:18 ` Michael S. Tsirkin
2017-07-04 11:03 ` Wei Wang [this message]
2017-07-06 0:08 ` [virtio-dev] " Michael S. Tsirkin
2017-07-06 0:08 ` [Qemu-devel] " Michael S. Tsirkin
2017-07-06 13:48 ` Michael S. Tsirkin
2017-07-06 13:48 ` [Qemu-devel] " Michael S. Tsirkin
2017-07-06 15:30 ` [virtio-dev] " Wang, Wei W
2017-07-06 15:30 ` [Qemu-devel] " 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=595B7617.4060203@intel.com \
--to=wei.w.wang@intel.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.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 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.