From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KnJM0-0001H5-7A for qemu-devel@nongnu.org; Tue, 07 Oct 2008 16:40:24 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KnJLz-0001GU-9L for qemu-devel@nongnu.org; Tue, 07 Oct 2008 16:40:23 -0400 Received: from [199.232.76.173] (port=53276 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KnJLy-0001GM-TL for qemu-devel@nongnu.org; Tue, 07 Oct 2008 16:40:23 -0400 Received: from mx2.redhat.com ([66.187.237.31]:40457) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KnJLy-0008El-EX for qemu-devel@nongnu.org; Tue, 07 Oct 2008 16:40:22 -0400 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id m97KeLiK026913 for ; Tue, 7 Oct 2008 16:40:21 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m97KeKdx024501 for ; Tue, 7 Oct 2008 16:40:20 -0400 Received: from zweiblum.travel.kraxel.org (vpn-4-165.str.redhat.com [10.32.4.165]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id m97KeJ1r008244 for ; Tue, 7 Oct 2008 16:40:19 -0400 Message-ID: <48EBC932.9010808@redhat.com> Date: Tue, 07 Oct 2008 22:40:18 +0200 From: Gerd Hoffmann MIME-Version: 1.0 Subject: Re: [Qemu-devel] [5323] Implement an fd pool to get real AIO with posix-aio References: <48EB8393.8020005@redhat.com> <48EB87EE.9050003@codemonkey.ws> In-Reply-To: <48EB87EE.9050003@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1 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: qemu-devel@nongnu.org Anthony Liguori wrote: >> Are there plans to support vectored block requests with the thread pool >> implementation? >> > > Yes, that's the primary reason for doing a new thread pool > implementation. Cool. > Of course, we need a zero-copy DMA API before such a > thing would make sense. Hmm, quick check of the IDE code indeed shows a copy happening there. Why is it needed? My xen disk backend doesn't copy data. Does that mean might have done something wrong? Does the virtio backend copy data too? Disclaimer: I don't know much about ide dma ... cheers, Gerd