From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EMRRa-0004hD-Cb for qemu-devel@nongnu.org; Mon, 03 Oct 2005 10:37:30 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EMRRY-0004gj-VO for qemu-devel@nongnu.org; Mon, 03 Oct 2005 10:37:29 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EMROZ-0003Jb-Gc for qemu-devel@nongnu.org; Mon, 03 Oct 2005 10:34:23 -0400 Received: from [195.184.98.160] (helo=virtualhost.dk) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1EMQpR-0001pO-JN for qemu-devel@nongnu.org; Mon, 03 Oct 2005 09:58:05 -0400 Received: from [62.242.22.158] (helo=router.home.kernel.dk) by virtualhost.dk with esmtp (Exim 3.36 #1) id 1EMQpQ-0002du-00 for qemu-devel@nongnu.org; Mon, 03 Oct 2005 15:58:04 +0200 Received: from nelson.home.kernel.dk ([192.168.0.33] helo=kernel.dk) by router.home.kernel.dk with esmtp (Exim 4.22) id 1EMQpO-0001pR-9y for qemu-devel@nongnu.org; Mon, 03 Oct 2005 15:58:02 +0200 Date: Mon, 3 Oct 2005 15:58:40 +0200 From: Jens Axboe Subject: Re: [Qemu-devel] [patch] non-blocking disk IO Message-ID: <20051003135837.GC3511@suse.de> References: <4340D479.7030301@stanfordalumni.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4340D479.7030301@stanfordalumni.org> 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 Mon, Oct 03 2005, John Coiner wrote: > > Non-blocking disk IO now works for any type of disk image, not just > "raw" format. There is no longer any format-specific code in the patch: > > http://people.brandeis.edu/~jcoiner/qemu_idedma/qemu_dma_patch.html > > You might want this patch if: > * you run a multitasking guest OS, > * you access a disk sometimes, and > * you wouldn't mind if QEMU ran a little faster. > > Why I have not got feedback in droves I do not understand ;) Why not use aio for this instead, seems like a better fit than spawning a thread per block device? That would still require a thread for handling completions, but you could easily just use a single completion thread for all devices for this as it would not need to do any real work. -- Jens Axboe