From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ln9QR-0002Ni-G8 for qemu-devel@nongnu.org; Fri, 27 Mar 2009 06:36:35 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ln9QM-0002L7-OM for qemu-devel@nongnu.org; Fri, 27 Mar 2009 06:36:34 -0400 Received: from [199.232.76.173] (port=56208 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ln9QM-0002Ku-E4 for qemu-devel@nongnu.org; Fri, 27 Mar 2009 06:36:30 -0400 Received: from mail1-relais-roc.national.inria.fr ([192.134.164.82]:46757) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.60) (envelope-from ) id 1Ln9QL-000439-UX for qemu-devel@nongnu.org; Fri, 27 Mar 2009 06:36:30 -0400 Received: from samy by const with local (Exim 4.69) (envelope-from ) id 1Ln9QK-0005PX-73 for qemu-devel@nongnu.org; Fri, 27 Mar 2009 11:36:28 +0100 Date: Fri, 27 Mar 2009 11:36:28 +0100 From: Samuel Thibault Subject: Re: [Qemu-devel] [PATCH] honor IDE_DMA_BUF_SECTORS Message-ID: <20090327103628.GF5408@const.bordeaux.inria.fr> References: <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> <20090326224229.GA7311@lst.de> <20090326232230.GF5458@const.famille.thibault.fr> <49CCA449.4010504@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <49CCA449.4010504@redhat.com> 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, le Fri 27 Mar 2009 13:02:49 +0300, a écrit : > Samuel Thibault wrote: > >Nothing in Linux makes filesystems and devices systematically read/write > >the amount of data that was requested. > > We're talking about the qemu block layer, not Linux. Well, in the part I quoted before my sentence: > At least for Linux I couldn't think of a way to introduce such an > arbitrary limit anyway. I believed you were talking about Linux never making short reads. > You're proposing to take the posix API rules and apply them to the > qemu block layer. No. I'm proposing to take into account that because of the posix API rules, we should fix our block layer. > But posix read/write does not fit how DMA works. A request should > either complete fully, or fail, leaving the destination (disk or > memory) in an undefined state. Sure. Again, please read what _I_ wrote: I'm not proposing to expose that into DMA, just make it genericly handled in the block layer. Samuel