qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Zhangleiqiang <zhangleiqiang@huawei.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	"Luohao (brian)" <brian.luohao@huawei.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Haofeng <haofeng@huawei.com>, leiqzhang <leiqzhang@gmail.com>
Subject: Re: [Qemu-devel] 答复:  question about performance of dataplane
Date: Thu, 4 Apr 2013 09:20:38 +0200	[thread overview]
Message-ID: <20130404072038.GA24402@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <3A6795EA1206904E94BEC8EF9DF109AE05D38653@szxeml510-mbx.china.huawei.com>

On Tue, Apr 02, 2013 at 02:02:54AM +0000, Zhangleiqiang wrote:
> 	I have also finished the perf testing under Fedora 17 using IOZone, and the results also shown that the performance of disk with dataplane enabled did not have advantage over non-dataplane.

virtio-blk data plane is a win for parallel I/O workloads (that means
iodepth > 1).  The advantage becomes clearer with SMP guests.

In other words the big advantage is that data plane processes requests
without blocking the QEMU main loop or vCPU threads.

If your guest has 1 vCPU and/or your benchmarks only do a single stream
of I/O requests, then the difference may not be measurable.

Stefan

  reply	other threads:[~2013-04-04  7:21 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 [this message]
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         ` [Qemu-devel] " Stefan Hajnoczi
2013-04-08 13:01           ` 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=20130404072038.GA24402@stefanha-thinkpad.redhat.com \
    --to=stefanha@redhat.com \
    --cc=brian.luohao@huawei.com \
    --cc=haofeng@huawei.com \
    --cc=leiqzhang@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).