From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G5e5S-0000ga-M6 for qemu-devel@nongnu.org; Wed, 26 Jul 2006 03:45:46 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G5e5R-0000fz-72 for qemu-devel@nongnu.org; Wed, 26 Jul 2006 03:45:45 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G5e5Q-0000fk-FO for qemu-devel@nongnu.org; Wed, 26 Jul 2006 03:45:44 -0400 Received: from [195.184.98.160] (helo=virtualhost.dk) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.52) id 1G5e6u-00044b-Pt for qemu-devel@nongnu.org; Wed, 26 Jul 2006 03:47:16 -0400 Received: from [62.242.22.158] (helo=router.home.kernel.dk) by virtualhost.dk with esmtp (Exim 3.36 #1) id 1G5e5P-00046l-00 for qemu-devel@nongnu.org; Wed, 26 Jul 2006 09:45:43 +0200 Received: from nelson.home.kernel.dk ([192.168.0.33] helo=kernel.dk) by router.home.kernel.dk with esmtp (Exim 4.51) id 1G5e5O-0000k8-9d for qemu-devel@nongnu.org; Wed, 26 Jul 2006 09:45:42 +0200 Date: Wed, 26 Jul 2006 09:45:36 +0200 From: Jens Axboe Subject: Re: [Qemu-devel] Re: high CPU load / async IO? Message-ID: <20060726074535.GT4044@suse.de> References: <20060725194316.GH4044@suse.de> <44C68124.3020809@bellard.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <44C68124.3020809@bellard.org> Content-Transfer-Encoding: quoted-printable Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Tue, Jul 25 2006, Fabrice Bellard wrote: > Jens Axboe wrote: > >On Tue, Jul 25 2006, Sven K=F6hler wrote: > > > >>>>>So the current thread-based async dma patch is really just the > >>>>>wrong long term solution. A more long term solution is likely in > >>>>>the works. It requires quite a bit of code modification though. > >>>> > >>>>I see. So in other words: > >>>> > >>>>don't ask for simple async I/O now. The more complex and flexible > >>>>sollution will follow soon. > >>> > >>>Yes, hopefully really soon. > >> > >>So i will wait patiently :-) > > > > > >Is anyone actively working on this, or is it just speculation? I'd > >greatly prefer (and might do, if no one is working on it and Fabrice > >would take it) do a libaio version, since that'll for sure perform > >the best on Linux. But a posixaio version might be saner, as that > >should work on other operating systems as well. > > > >Fabrice, can you let people know what you would prefer? >=20 > I am working on an implementation and the first version will use the > posix aio and possibly the Windows ReadFile/WriteFile overlapped I/Os. > Anthony Liguori got a pre version of the code, but it is not > commitable yet. Sounds good, so at least it's on its way :-) It's on of those big items left on the TODO, so will be good to see go in. Then one should implement an ahci host controller for queued command support next... --=20 Jens Axboe