From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LmooO-0005T3-5s for qemu-devel@nongnu.org; Thu, 26 Mar 2009 08:35:56 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LmooJ-0005JT-H2 for qemu-devel@nongnu.org; Thu, 26 Mar 2009 08:35:55 -0400 Received: from [199.232.76.173] (port=36567 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LmooJ-0005JH-AH for qemu-devel@nongnu.org; Thu, 26 Mar 2009 08:35:51 -0400 Received: from smtp02.citrix.com ([66.165.176.63]:33197) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LmooI-0004GM-VN for qemu-devel@nongnu.org; Thu, 26 Mar 2009 08:35:51 -0400 Received: from [10.80.225.184] ([10.80.225.184]) by smtp01.ad.xensource.com (8.13.1/8.13.1) with ESMTP id n2QCZmWg000757 for ; Thu, 26 Mar 2009 05:35:48 -0700 Message-ID: <49CB74EC.6020304@eu.citrix.com> Date: Thu, 26 Mar 2009 12:28:28 +0000 From: Stefano Stabellini MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] honor IDE_DMA_BUF_SECTORS References: <49CA3591.1010309@eu.citrix.com> <49CA4C3D.1070705@redhat.com> <49CA59AE.8060605@eu.citrix.com> <49CA5F9F.5040203@redhat.com> <49CA60BA.5060704@eu.citrix.com> <49CA6E4A.4080408@eu.citrix.com> <49CB5793.4030006@redhat.com> <49CB599D.6000701@eu.citrix.com> <49CB5FA0.10101@redhat.com> <49CB6AF7.3080604@eu.citrix.com> <49CB70AC.3060900@redhat.com> In-Reply-To: <49CB70AC.3060900@redhat.com> 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" Avi Kivity wrote: >> When preadv/pwritev are in place I could limit the transfer size >> directly in raw_aio_preadv\pwritev but I would also have to update the >> iovector size field to reflect that and I think is a little bit ugly. >> > > Just copy the iovec for each sub-request. > OK, I'll see about that when the preadv and pwritev are actually implemented. Meanwhile I'll keep the patch I sent before in our tree only (unless someone else is interested in a way to limit dma transfer size for any reason).