From: Stefan Hajnoczi <stefanha@gmail.com>
To: 浩樊啊 <fanh2010@foxmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] performance in io virtulization
Date: Tue, 22 Dec 2015 15:58:59 +0800 [thread overview]
Message-ID: <20151222075859.GC23256@stefanha-x1.localdomain> (raw)
In-Reply-To: <tencent_07F913A449E957343322ED37@qq.com>
[-- Attachment #1: Type: text/plain, Size: 513 bytes --]
On Mon, Dec 21, 2015 at 12:40:00PM +0800, 浩樊啊 wrote:
> i use qemu 2.2 and zhe vm kernel is 3.18i use fio do experiments in host and vm:
> 4k randwrite/read ioengine=libaio
> host: vm:
> randread about 200M/S randread about 190M/S
> randwrite about 160M/S randwrite about 65M/S
>
>
> i tried multiqueue and dataplane ,but no improvement
Please post the fio job file and QEMU command-line.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-12-22 7:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 4:40 [Qemu-devel] performance in io virtulization =?gb18030?B?usa3rrCh?=
2015-12-22 7:58 ` Stefan Hajnoczi [this message]
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=20151222075859.GC23256@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=fanh2010@foxmail.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).