From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Qemu-devel] Re: [PATCH 1/3] Refactor AIO interface to allow other AIO implementations Date: Fri, 18 Apr 2008 19:32:16 +0300 Message-ID: <4808CD10.8010609@qumranet.com> References: <1208460412-27567-1-git-send-email-aliguori@us.ibm.com> <20080417193807.GB11916@redhat.com> <4807A7EC.6040408@us.ibm.com> <20080417200024.GC11916@redhat.com> <20080418124319.GC25089@shareable.org> <4808BCF3.3060200@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel@lists.sourceforge.net, Marcelo Tosatti , qemu-devel@nongnu.org To: Anthony Liguori Return-path: In-Reply-To: <4808BCF3.3060200@us.ibm.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces@lists.sourceforge.net Errors-To: kvm-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org Anthony Liguori wrote: > Right now, not specifying the -aio option is equivalent to your proposed > -aio auto. > > I guess I should include an info aio to let the user know what type of > aio they are using. We can add selection criteria later but > semantically, not specifying an explicit -aio option allows QEMU to > choose whichever one it thinks is best. > > For the majority of deployments posix aio should be sufficient. The few that need something else can use Linux aio. Of course, a managed environment can use Linux aio unconditionally if knows the kernel has all the needed goodies. -- Any sufficiently difficult bug is indistinguishable from a feature. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone