From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ln9gL-0007eU-Ht for qemu-devel@nongnu.org; Fri, 27 Mar 2009 06:53:01 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ln9gG-0007b1-1o for qemu-devel@nongnu.org; Fri, 27 Mar 2009 06:53:00 -0400 Received: from [199.232.76.173] (port=44479 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ln9gF-0007at-Pd for qemu-devel@nongnu.org; Fri, 27 Mar 2009 06:52:55 -0400 Received: from mx2.redhat.com ([66.187.237.31]:52663) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ln9gF-0007ZY-5A for qemu-devel@nongnu.org; Fri, 27 Mar 2009 06:52:55 -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 n2RAqsLj010670 for ; Fri, 27 Mar 2009 06:52:54 -0400 Message-ID: <49CCB02B.40201@redhat.com> Date: Fri, 27 Mar 2009 13:53:31 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] honor IDE_DMA_BUF_SECTORS References: <49CB6AF7.3080604@eu.citrix.com> <49CB70AC.3060900@redhat.com> <20090326124719.GL5642@const.bordeaux.inria.fr> <49CB7C0F.7010507@redhat.com> <20090326153021.GP5642@const.bordeaux.inria.fr> <49CBCA3C.2030909@redhat.com> <20090326184814.GC5458@const.famille.thibault.fr> <49CBDA22.3070600@redhat.com> <20090326231801.GE5458@const.famille.thibault.fr> <49CCA1CF.4000003@redhat.com> <20090327103238.GE5408@const.bordeaux.inria.fr> In-Reply-To: <20090327103238.GE5408@const.bordeaux.inria.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable 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 Samuel Thibault wrote: > Avi Kivity, le Fri 27 Mar 2009 12:52:15 +0300, a =E9crit : > =20 >> However implementing DMA limits like you propose=20 >> (IDE_DMA_BUF_SECTORS) will not fix the bug, only reduce performance. >> =20 > > Have you read what I wrote? v > =20 You can't have a good flamewar if you read what people actually write. =20 Maybe I'm confused by $subject. >> block-raw-posix need not do that, just a while loop. >> =20 > > For the synchronous interface, yes. For the asynchronous interface, > short reads could happen too... (unfortunately we are aware of that too > late for queuing other requests and getting efficiency). > =20 Currently block-raw-posix uses synchronous I/O even for asynchronous=20 requests (using threads) so the fix is the same in both cases. --=20 I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.