From: Avi Kivity <avi@redhat.com>
To: Dustin Kirkland <kirkland@canonical.com>
Cc: Bernhard Schmidt <berni@birkenwald.de>, kvm@vger.kernel.org
Subject: Re: linux-aio usable?
Date: Mon, 08 Mar 2010 16:26:37 +0200 [thread overview]
Message-ID: <4B95091D.4020307@redhat.com> (raw)
In-Reply-To: <d9c105ea1003080625y1fabe4aagb910edc6ef84adb3@mail.gmail.com>
On 03/08/2010 04:25 PM, Dustin Kirkland wrote:
> On Mon, Mar 8, 2010 at 3:48 AM, Avi Kivity<avi@redhat.com> wrote:
>
>> On 03/08/2010 11:48 AM, Bernhard Schmidt wrote:
>>
>>> 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).
>>>>
>>> What does "work well" mean in this context? Potential dataloss?
>>>
>> No, it becomes synchronous (=extra slow).
>>
> But for this to happen, the user would have had to consciously enter
> into the situation by creating/using a non block device,
> non-pre-allocated backing disk AND specify the aio=native option,
> correct?
>
>
I thought there was some autodetection involved, but perhaps I just
imagined it.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-03-08 14:26 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 [this message]
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=4B95091D.4020307@redhat.com \
--to=avi@redhat.com \
--cc=berni@birkenwald.de \
--cc=kirkland@canonical.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.