From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LmyHY-0001Mk-2d for qemu-devel@nongnu.org; Thu, 26 Mar 2009 18:42:40 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LmyHT-0001IZ-E2 for qemu-devel@nongnu.org; Thu, 26 Mar 2009 18:42:39 -0400 Received: from [199.232.76.173] (port=35455 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LmyHT-0001IN-5i for qemu-devel@nongnu.org; Thu, 26 Mar 2009 18:42:35 -0400 Received: from verein.lst.de ([213.95.11.210]:40983) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60) (envelope-from ) id 1LmyHR-0006NW-Ki for qemu-devel@nongnu.org; Thu, 26 Mar 2009 18:42:34 -0400 Received: from verein.lst.de (localhost [127.0.0.1]) by verein.lst.de (8.12.3/8.12.3/Debian-7.1) with ESMTP id n2QMgUIF007525 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 26 Mar 2009 23:42:30 +0100 Received: (from hch@localhost) by verein.lst.de (8.12.3/8.12.3/Debian-6.6) id n2QMgTXO007523 for qemu-devel@nongnu.org; Thu, 26 Mar 2009 23:42:29 +0100 Date: Thu, 26 Mar 2009 23:42:29 +0100 From: Christoph Hellwig Subject: Re: [Qemu-devel] [PATCH] honor IDE_DMA_BUF_SECTORS Message-ID: <20090326224229.GA7311@lst.de> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49CB6AF7.3080604@eu.citrix.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 On Thu, Mar 26, 2009 at 11:45:59AM +0000, Stefano Stabellini wrote: > My problem is that my block driver has a size limit for read and write > operations. So fix your driver. I assume that driver in question is a qemu BlockDriver and not a kernel driver behind block-raw-posix.c? At least for Linux I couldn't think of a way to introduce such an arbitrary limit anyway.