From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JmtWO-0004pV-24 for qemu-devel@nongnu.org; Fri, 18 Apr 2008 12:33:08 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JmtWM-0004p4-GX for qemu-devel@nongnu.org; Fri, 18 Apr 2008 12:33:07 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JmtWM-0004p1-EK for qemu-devel@nongnu.org; Fri, 18 Apr 2008 12:33:06 -0400 Received: from bzq-179-150-194.static.bezeqint.net ([212.179.150.194] helo=il.qumranet.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JmtWM-0005KW-Gf for qemu-devel@nongnu.org; Fri, 18 Apr 2008 12:33:06 -0400 Message-ID: <4808CD10.8010609@qumranet.com> Date: Fri, 18 Apr 2008 19:32:16 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [kvm-devel] [Qemu-devel] Re: [PATCH 1/3] Refactor AIO interface to allow other AIO implementations 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> In-Reply-To: <4808BCF3.3060200@us.ibm.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: kvm-devel@lists.sourceforge.net, Marcelo Tosatti , qemu-devel@nongnu.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.