From: Rusty Russell <rusty@rustcorp.com.au>
To: Dongsu Park <dongsu.park@profitbricks.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: virtio-blk performance regression and qemu-kvm
Date: Wed, 22 Feb 2012 08:46:41 +1030 [thread overview]
Message-ID: <87obsr6ddi.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20120221164508.GB950@gmail.com>
On Tue, 21 Feb 2012 17:45:08 +0100, Dongsu Park <dongsu.park@profitbricks.com> wrote:
> Hi Rusty,
>
> On 13.02.2012 10:25, Rusty Russell wrote:
> > On Fri, 10 Feb 2012 15:36:39 +0100, Dongsu Park <dongsu.park@profitbricks.com> wrote:
> > > Hi,
> > >
> > > Recently I observed performance regression regarding virtio-blk,
> > > especially different IO bandwidths between qemu-kvm 0.14.1 and 1.0.
> > > So I want to share the benchmark results, and ask you what the reason
> > > would be.
> >
> > Interesting. There are two obvious possibilities here. One is that
> > qemu has regressed, the other is that virtio_blk has regressed; the new
> > qemu may negotiate new features. Please do the following in the guest
> > with old and new qemus:
> >
> > cat /sys/class/block/vdb/device/features
> >
> > (eg, here that gives: 0010101101100000000000000000100e0).
>
> I did that on guest VM, using both qemu-kvm 0.14.1 and 1.0.
> (cat /sys/class/block/vdb/device/features)
>
> using qemu-kvm 0.14.1:
>
> 0010101101100000000000000000100000000000000000000000000000000000
>
> using qemu-kvm 1.0:
>
> 0010101101100000000000000000110000000000000000000000000000000000
>
> >From my understanding, both of them have the same virtio features.
> Please correct me if I'm wrong.
Well, 1.0 supports event index (feature 29), but that's the only
difference.
This seems very much like a qemu regression.
Thanks,
Rusty.
next prev parent reply other threads:[~2012-02-21 22:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 14:36 virtio-blk performance regression and qemu-kvm Dongsu Park
2012-02-12 23:55 ` Rusty Russell
2012-02-21 16:45 ` Dongsu Park
2012-02-21 22:16 ` Rusty Russell [this message]
2012-02-13 11:57 ` Stefan Hajnoczi
2012-02-21 15:57 ` Dongsu Park
2012-02-21 17:27 ` Stefan Hajnoczi
2012-02-22 16:48 ` Dongsu Park
2012-02-22 19:53 ` Stefan Hajnoczi
2012-02-28 16:39 ` Martin Mailand
2012-02-28 17:05 ` Stefan Hajnoczi
2012-02-28 17:15 ` Martin Mailand
2012-02-29 8:38 ` Stefan Hajnoczi
2012-02-29 13:12 ` Martin Mailand
2012-02-29 13:44 ` Stefan Hajnoczi
2012-02-29 13:52 ` Stefan Hajnoczi
2012-03-05 16:13 ` Martin Mailand
2012-03-05 16:35 ` Stefan Hajnoczi
2012-03-05 16:44 ` Martin Mailand
2012-03-06 12:59 ` Stefan Hajnoczi
2012-03-06 22:07 ` [Qemu-devel] " Reeted
2012-03-07 8:04 ` Stefan Hajnoczi
2012-03-07 14:21 ` Reeted
2012-03-07 14:33 ` Stefan Hajnoczi
2012-03-07 10:39 ` Martin Mailand
2012-03-07 11:21 ` Paolo Bonzini
2012-03-06 14:32 ` Dongsu Park
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=87obsr6ddi.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=dongsu.park@profitbricks.com \
--cc=kvm@vger.kernel.org \
--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