From: Stefan Hajnoczi <stefanha@gmail.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Zhangleiqiang <zhangleiqiang@huawei.com>,
"Luohao (brian)" <brian.luohao@huawei.com>,
Haofeng <haofeng@huawei.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"stefanha@redhat.com" <stefanha@redhat.com>,
leiqzhang <leiqzhang@gmail.com>
Subject: Re: [Qemu-devel] question about performance of dataplane
Date: Mon, 8 Apr 2013 13:08:41 +0200 [thread overview]
Message-ID: <20130408110841.GE12076@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <874nfio2pw.fsf@codemonkey.ws>
On Sun, Apr 07, 2013 at 09:05:47AM -0500, Anthony Liguori wrote:
> Zhangleiqiang <zhangleiqiang@huawei.com> writes:
>
> > Hi, Stefan:
> >
> > I have done some testing to compare the performance of dataplane and non-dataplane. But the result did not meet my expectations, the performance of disk with dataplane enabled did not have advantage over non-dataplane.
> >
> > The following contains the environment info and testing results. Does my testing method or testing environment have something wrong ? Could you give me some advice? I can provide more information if need.
> >
> >
> > 1. Environment:
> > a). Qemu 1.4 master branch
> > b). kernel: 3.5.0-2.fc17.x86_64
> > c). virtual disks location: the same local SATA harddisk
> > with ext4 fs
>
> I doubt you'll see any performance difference with a single SATA drive.
> There's no real parallelism possible as you have exactly one spindle
> available.
Sorry for the delay, catching up on emails after my Easter vacation.
I agree with Anthony here. It seems your benchmark configuration is
bottlenecked below the point where data plane makes a difference.
Stefan
next prev parent reply other threads:[~2013-04-08 11:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 15:10 [Qemu-devel] dataplane bug: fail to start Windows VM with dataplane enable 张磊强
2013-03-27 13:32 ` Stefan Hajnoczi
2013-03-27 14:02 ` Stefan Hajnoczi
2013-03-27 15:15 ` Stefan Hajnoczi
2013-03-27 15:41 ` Stefan Hajnoczi
2013-03-28 4:03 ` [Qemu-devel] 回复: " leiqzhang
2013-04-01 13:34 ` [Qemu-devel] question about performance of dataplane Zhangleiqiang
2013-04-02 2:02 ` [Qemu-devel] 答复: " Zhangleiqiang
2013-04-04 7:20 ` Stefan Hajnoczi
2013-04-07 11:31 ` [Qemu-devel] 答复: " Zhangleiqiang
2013-04-07 11:42 ` Abel Gordon
2013-04-07 13:34 ` [Qemu-devel] 答复: " Zhangleiqiang
2013-04-07 14:01 ` Abel Gordon
[not found] ` <CAO-gD_kYmnph95UGUVbGBcvNqZ4zKDbzBdRXh+MD7KSoZFgyrw@mail.gmail.com>
[not found] ` <OF71AA8EBF.56A0BFE1-ONC2257B46.0059C6C3-C2257B46.005B8DA6@il.ibm. <3A6795EA1206904E94BEC8EF9DF109AE05D3AD3F@szxeml510-mbx.china.huawei.com>
2013-04-07 16:40 ` Abel Gordon
2013-04-08 9:06 ` [Qemu-devel] 答复: " Zhangleiqiang
2013-04-08 11:04 ` Abel Gordon
2013-04-08 11:13 ` Zhangleiqiang
2013-04-08 11:31 ` Abel Gordon
2013-04-07 14:05 ` [Qemu-devel] " Anthony Liguori
2013-04-08 3:13 ` [Qemu-devel] 答复: " Zhangleiqiang
2013-04-08 11:08 ` Stefan Hajnoczi [this message]
2013-04-08 13:01 ` [Qemu-devel] " Zhangleiqiang
2013-04-09 11:49 ` 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=20130408110841.GE12076@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=anthony@codemonkey.ws \
--cc=brian.luohao@huawei.com \
--cc=haofeng@huawei.com \
--cc=leiqzhang@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=zhangleiqiang@huawei.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).