public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Avi Kivity <avi@redhat.com>
Cc: Bernhard Schmidt <berni@birkenwald.de>, kvm@vger.kernel.org
Subject: Re: linux-aio usable?
Date: Mon, 8 Mar 2010 08:00:21 -0500	[thread overview]
Message-ID: <20100308130021.GA17498@infradead.org> (raw)
In-Reply-To: <4B94BF05.20609@redhat.com>

On Mon, Mar 08, 2010 at 11:10:29AM +0200, Avi Kivity wrote:
>> Are there any potential pitfalls?
>>    
>
> It won't work well unless running on a block device (partition or LVM).

It will actually work well on pre-allocated filesystem images, at least
on XFS and NFS.

The real pitfal is that cache=none is required for kernel support as
it only supports O_DIRECT.

>> Is there any reason one should not compile that feature by default?

It's compiled by default if libaio and it's development headers are
found.

>> Does it do anything if not explicitly run with aio=native?

No.


  parent reply	other threads:[~2010-03-08 13:00 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
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 [this message]
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=20100308130021.GA17498@infradead.org \
    --to=hch@infradead.org \
    --cc=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