From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M8Zne-0004PH-DX for qemu-devel@nongnu.org; Mon, 25 May 2009 09:01:06 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M8ZnZ-0004LD-5H for qemu-devel@nongnu.org; Mon, 25 May 2009 09:01:05 -0400 Received: from [199.232.76.173] (port=45359 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M8ZnY-0004Kv-5L for qemu-devel@nongnu.org; Mon, 25 May 2009 09:01:00 -0400 Date: Mon, 25 May 2009 15:00:34 +0200 From: Christoph Hellwig Subject: Re: [Qemu-devel] Do we need CONFIG_AIO? Message-ID: <20090525130034.GA18197@lst.de> References: <20090525082151.GA4107@lst.de> <4A1A85B4.3060200@eu.citrix.com> <20090525122929.GA16576@lst.de> <20090525125852.GK5909@const.bordeaux.inria.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090525125852.GK5909@const.bordeaux.inria.fr> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Samuel Thibault Cc: "qemu-devel@nongnu.org" , Christoph Hellwig , Stefano Stabellini On Mon, May 25, 2009 at 02:58:52PM +0200, Samuel Thibault wrote: > qemu on MiniOS is used to provide efficient full virtualisation, so yes > it's performance sensitive, but for performances we use a block-vbd > interface. Keeping the block-posix interface for non-performance > critical resources that can not go through vbd is still important, so we > need to be able to compile it. Apparently all this is not in upstream qemu, right? I really don't see the reason to keep all this stuff around for out of tree bits only given it is a significant burden.