qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: =?gb18030?B?usa3rrCh?= <fanh2010@foxmail.com>
To: =?gb18030?B?cWVtdS1kZXZlbA==?= <qemu-devel@nongnu.org>
Cc: =?gb18030?B?U3RlZmFuIEhham5vY3pp?= <stefanha@gmail.com>
Subject: [Qemu-devel] performance in io virtulization
Date: Mon, 21 Dec 2015 12:40:00 +0800	[thread overview]
Message-ID: <tencent_07F913A449E957343322ED37@qq.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 370 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 687 bytes --]

             reply	other threads:[~2015-12-21  4:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-21  4:40 =?gb18030?B?usa3rrCh?= [this message]
2015-12-22  7:58 ` [Qemu-devel] performance in io virtulization 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=tencent_07F913A449E957343322ED37@qq.com \
    --to=fanh2010@foxmail.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).