From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH v5 0/4] virtio: Use ioeventfd for virtqueue notify
Date: Mon, 13 Dec 2010 18:12:19 +0200 [thread overview]
Message-ID: <20101213161219.GA6715@redhat.com> (raw)
In-Reply-To: <AANLkTimrVzxcwxrTya0=Av2NDfbP_2tEvr6+vPjQzwJx@mail.gmail.com>
On Mon, Dec 13, 2010 at 03:27:06PM +0000, Stefan Hajnoczi wrote:
> On Mon, Dec 13, 2010 at 1:36 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
> > On Mon, Dec 13, 2010 at 03:35:38PM +0200, Michael S. Tsirkin wrote:
> >> On Mon, Dec 13, 2010 at 01:11:27PM +0000, Stefan Hajnoczi wrote:
> >> > Fresh results:
> >> >
> >> > 192.168.0.1 - host (runs netperf)
> >> > 192.168.0.2 - guest (runs netserver)
> >> >
> >> > host$ src/netperf -H 192.168.0.2 -- -m 200
> >> >
> >> > ioeventfd=on
> >> > TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.0.2
> >> > (192.168.0.2) port 0 AF_INET
> >> > Recv Send Send
> >> > Socket Socket Message Elapsed
> >> > Size Size Size Time Throughput
> >> > bytes bytes bytes secs. 10^6bits/sec
> >> > 87380 16384 200 10.00 1759.25
> >> >
> >> > ioeventfd=off
> >> > TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.0.2
> >> > (192.168.0.2) port 0 AF_INET
> >> > Recv Send Send
> >> > Socket Socket Message Elapsed
> >> > Size Size Size Time Throughput
> >> > bytes bytes bytes secs. 10^6bits/sec
> >> >
> >> > 87380 16384 200 10.00 1757.15
> >> >
> >> > The results vary approx +/- 3% between runs.
> >> >
> >> > Invocation:
> >> > $ x86_64-softmmu/qemu-system-x86_64 -m 4096 -enable-kvm -netdev
> >> > type=tap,id=net0,ifname=tap0,script=no,downscript=no -device
> >> > virtio-net-pci,netdev=net0,ioeventfd=on|off -vnc :0 -drive
> >> > if=virtio,cache=none,file=$HOME/rhel6-autobench-raw.img
> >> >
> >> > I am running qemu.git with v5 patches, based off
> >> > 36888c6335422f07bbc50bf3443a39f24b90c7c6.
> >> >
> >> > Host:
> >> > 1 Quad-Core AMD Opteron(tm) Processor 2350 @ 2 GHz
> >> > 8 GB RAM
> >> > RHEL 6 host
> >> >
> >> > Next I will try the patches on latest qemu-kvm.git
> >> >
> >> > Stefan
> >>
> >> One interesting thing is that I put virtio-net earlier on
> >> command line.
> >
> > Sorry I mean I put it after disk, you put it before.
>
> I can't find a measurable difference when swapping -drive and -netdev.
One other concern I have is that we are apparently using
ioeventfd for all VQs. E.g. for virtio-net we probably should not
use it for the control VQ - it's a waste of resources.
> Can you run the same test with vhost? I assume it still outperforms
> userspace virtio for small message sizes? I'm interested because that
> also uses ioeventfd.
>
> I am wondering if the iothread differences between qemu.git and
> qemu-kvm.git can explain the performance results we see. In
> particular, qemu.git produces the same (high) throughput whether
> ioeventfd is on or off.
>
> Stefan
next prev parent reply other threads:[~2010-12-13 16:12 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-12 15:02 [Qemu-devel] [PATCH v5 0/4] virtio: Use ioeventfd for virtqueue notify Stefan Hajnoczi
2010-12-12 15:02 ` [Qemu-devel] [PATCH v5 1/4] virtio-pci: Rename bugs field to flags Stefan Hajnoczi
2010-12-12 15:02 ` [Qemu-devel] [PATCH v5 2/4] virtio-pci: Use ioeventfd for virtqueue notify Stefan Hajnoczi
2011-01-24 18:54 ` Kevin Wolf
2011-01-24 19:36 ` Michael S. Tsirkin
2011-01-24 19:48 ` Kevin Wolf
2011-01-24 19:47 ` Michael S. Tsirkin
2011-01-24 20:05 ` Kevin Wolf
2011-01-25 7:12 ` Stefan Hajnoczi
2011-01-25 9:49 ` Stefan Hajnoczi
2011-01-25 9:54 ` Stefan Hajnoczi
2011-01-25 11:27 ` Michael S. Tsirkin
2011-01-25 13:20 ` Stefan Hajnoczi
2011-01-25 14:07 ` Stefan Hajnoczi
2011-01-25 19:18 ` Anthony Liguori
2011-01-25 19:45 ` Stefan Hajnoczi
2011-01-25 19:51 ` Anthony Liguori
2011-01-25 19:59 ` Stefan Hajnoczi
2011-01-26 0:18 ` Anthony Liguori
2010-12-12 15:02 ` [Qemu-devel] [PATCH v5 3/4] virtio-pci: Don't use ioeventfd on old kernels Stefan Hajnoczi
2010-12-12 15:02 ` [Qemu-devel] [PATCH v5 4/4] docs: Document virtio PCI -device ioeventfd=on|off Stefan Hajnoczi
2010-12-12 15:14 ` [Qemu-devel] Re: [PATCH v5 0/4] virtio: Use ioeventfd for virtqueue notify Stefan Hajnoczi
2010-12-12 20:41 ` Michael S. Tsirkin
2010-12-12 20:42 ` Michael S. Tsirkin
2010-12-12 20:56 ` Michael S. Tsirkin
2010-12-12 21:09 ` Michael S. Tsirkin
2010-12-13 10:24 ` Stefan Hajnoczi
2010-12-13 10:38 ` Michael S. Tsirkin
2010-12-13 13:11 ` Stefan Hajnoczi
2010-12-13 13:35 ` Michael S. Tsirkin
2010-12-13 13:36 ` Michael S. Tsirkin
2010-12-13 14:06 ` Stefan Hajnoczi
2010-12-13 15:27 ` Stefan Hajnoczi
2010-12-13 16:00 ` Michael S. Tsirkin
2010-12-13 16:29 ` Stefan Hajnoczi
2010-12-13 16:30 ` Michael S. Tsirkin
2010-12-13 16:12 ` Michael S. Tsirkin [this message]
2010-12-13 16:28 ` Stefan Hajnoczi
2010-12-13 17:57 ` Stefan Hajnoczi
2010-12-13 18:52 ` Michael S. Tsirkin
2010-12-15 11:42 ` Stefan Hajnoczi
2010-12-15 11:48 ` Stefan Hajnoczi
2010-12-15 12:00 ` Michael S. Tsirkin
2010-12-15 12:14 ` Michael S. Tsirkin
2010-12-15 12:59 ` Stefan Hajnoczi
2010-12-16 16:40 ` Stefan Hajnoczi
2010-12-16 23:39 ` Michael S. Tsirkin
2010-12-19 14:49 ` Michael S. Tsirkin
2011-01-06 16:41 ` Stefan Hajnoczi
2011-01-06 17:04 ` Michael S. Tsirkin
2011-01-06 18:00 ` Michael S. Tsirkin
2011-01-07 8:56 ` Stefan Hajnoczi
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=20101213161219.GA6715@redhat.com \
--to=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).