From: Avi Kivity <avi@redhat.com>
To: Bernhard Schmidt <berni@birkenwald.de>
Cc: kvm@vger.kernel.org
Subject: Re: linux-aio usable?
Date: Mon, 08 Mar 2010 11:10:29 +0200 [thread overview]
Message-ID: <4B94BF05.20609@redhat.com> (raw)
In-Reply-To: <hn1ktj$5gh$1@dough.gmane.org>
On 03/08/2010 03:46 AM, Bernhard Schmidt wrote:
> Hi,
>
> sorry for this pretty generic question, I did not find any real pros and
> cons on the net anywhere, but I might just have missed them.
>
> In a pure x86_64 environment (~2.6.32 vanilla kernel, 0.12.3 qemu-kvm),
> is enabling linux-aio in KVM a good idea?
Yes.
> What are the
> advantages/disadvantages?
It's faster.
> Are there any potential pitfalls?
>
It won't work well unless running on a block device (partition or LVM).
> The reason I'm asking is that there has been some traffic on the list
> about it, so it seems to be something people want to get working.
> qemu-kvm in Ubuntu Lucid is currently not compiled with that option.
> I've made a local version with aio and it seems to work fine (and
> performs a bit better at first glance).
>
> Is there any reason one should not compile that feature by default?
>
Not to my knowledge.
> Does it do anything if not explicitly run with aio=native?
>
IIUC, no.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-03-08 9:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 1:46 linux-aio usable? Bernhard Schmidt
2010-03-08 9:10 ` Avi Kivity [this message]
2010-03-08 9:48 ` Bernhard Schmidt
2010-03-08 9:48 ` Avi Kivity
2010-03-08 14:25 ` Dustin Kirkland
2010-03-08 14:26 ` Avi Kivity
2010-03-08 16:28 ` Anthony Liguori
2010-03-08 16:36 ` Avi Kivity
2010-03-08 13:00 ` Christoph Hellwig
2010-03-08 20:11 ` Michael Tokarev
2010-03-08 20:19 ` Michael Tokarev
2010-03-09 9:08 ` Avi Kivity
2010-03-09 9:19 ` Michael Tokarev
2010-03-09 10:05 ` Avi Kivity
2010-03-09 14:12 ` Christoph Hellwig
2010-03-08 21:27 ` Nikola Ciprich
2010-03-08 21:46 ` Brian Jackson
2010-03-09 9:09 ` Avi Kivity
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=4B94BF05.20609@redhat.com \
--to=avi@redhat.com \
--cc=berni@birkenwald.de \
--cc=kvm@vger.kernel.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