From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KnEib-0002vw-0f for qemu-devel@nongnu.org; Tue, 07 Oct 2008 11:43:25 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KnEiY-0002us-Kd for qemu-devel@nongnu.org; Tue, 07 Oct 2008 11:43:23 -0400 Received: from [199.232.76.173] (port=41448 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KnEiY-0002ue-D5 for qemu-devel@nongnu.org; Tue, 07 Oct 2008 11:43:22 -0400 Received: from mx2.redhat.com ([66.187.237.31]:50217) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KnEiX-00008B-Jo for qemu-devel@nongnu.org; Tue, 07 Oct 2008 11:43: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 m97FhImv028610 for ; Tue, 7 Oct 2008 11:43:18 -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 m97FhHp7017741 for ; Tue, 7 Oct 2008 11:43:17 -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 m97FhGJA002886 for ; Tue, 7 Oct 2008 11:43:16 -0400 Message-ID: <48EB8393.8020005@redhat.com> Date: Tue, 07 Oct 2008 17:43:15 +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: In-Reply-To: Content-Type: text/plain; charset=UTF-8 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: > The fundamental problem with posix-aio is that it limits itself to one thread > per-file descriptor. I don't know why this is, but this patch provides a simple > mechanism to work around this (duplicating the file descriptor). > > This isn't a great solution, but it seems like a reasonable intermediate step > between posix-aio and a custom thread-pool to replace it. Are there plans to support vectored block requests with the thread pool implementation? cheers, Gerd