From: Eric Auger <eric.auger@linaro.org>
To: qemu list <qemu-devel@nongnu.org>, "Michael S. Tsirkin" <mst@redhat.com>
Subject: [Qemu-devel] [question] virtio-net-device and multi-queue option
Date: Fri, 19 Sep 2014 02:10:56 +0200 [thread overview]
Message-ID: <541B7490.6080206@linaro.org> (raw)
Hi,
I am currently doing some benchmarks using virtio-net-device using
virtio-mmio (non PCI) with qemu_system_arm with KVM. Purpose is to
compare with device passthrough performance.
I heard about the availability of a multi-queue option that greatly
improves the performance but I currently fail in enabling it.
Please could someone explain me how to turn that feature on? My current
virtio-net options simply are:
-netdev tap,id=tap0,ifname="tap0" \
-device virtio-net-device,netdev=tap0
Also are there any "easy" tunings I can play with to try to reach the
best performance.
Thank you in advance
Best Regards
Eric
next reply other threads:[~2014-09-19 0:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 0:10 Eric Auger [this message]
2014-09-19 1:42 ` [Qemu-devel] [question] virtio-net-device and multi-queue option Gonglei (Arei)
2014-09-19 2:23 ` Eric Auger
2014-09-19 2:30 ` Gonglei (Arei)
2014-09-19 17:09 ` Eric Auger
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=541B7490.6080206@linaro.org \
--to=eric.auger@linaro.org \
--cc=mst@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 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).