From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: linux-aio usable? Date: Mon, 08 Mar 2010 16:26:37 +0200 Message-ID: <4B95091D.4020307@redhat.com> References: <4B94BF05.20609@redhat.com> <20100308094801.GA24943@schleppi.birkenwald.de> <4B94C806.9000209@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Bernhard Schmidt , kvm@vger.kernel.org To: Dustin Kirkland Return-path: Received: from mx1.redhat.com ([209.132.183.28]:59818 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755136Ab0CHO0z (ORCPT ); Mon, 8 Mar 2010 09:26:55 -0500 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 03/08/2010 04:25 PM, Dustin Kirkland wrote: > On Mon, Mar 8, 2010 at 3:48 AM, Avi Kivity 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