From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=41076 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OcGtF-0003xu-Dk for qemu-devel@nongnu.org; Fri, 23 Jul 2010 07:58:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OcGs4-0002N4-K0 for qemu-devel@nongnu.org; Fri, 23 Jul 2010 07:56:57 -0400 Received: from mx1.redhat.com ([209.132.183.28]:5035) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OcGs4-0002Mn-4x for qemu-devel@nongnu.org; Fri, 23 Jul 2010 07:56:56 -0400 Message-ID: <4C498382.2020904@redhat.com> Date: Fri, 23 Jul 2010 13:56:50 +0200 From: Kevin Wolf MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] block: default to 0 minimal / optiomal I/O size References: <20100723073504.GA28166@lst.de> <4C4973E4.5030502@redhat.com> <20100723113046.GA8898@lst.de> In-Reply-To: <20100723113046.GA8898@lst.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Christoph Hellwig Cc: qemu-devel@nongnu.org Am 23.07.2010 13:30, schrieb Christoph Hellwig: > On Fri, Jul 23, 2010 at 12:50:12PM +0200, Kevin Wolf wrote: >> This isn't reverting to the state before we reported anything, but it >> reports values of 0 now. Is this defined for both virtio-blk and SCSI to >> mean the same as no report at all? Or should we rather not advertise >> VIRTIO_BLK_F_TOPOLOGY (and the SCSI equivalent) in this case? > > For scsi it's explicitly defined that way, and there is not equivalent > to the VIRTIO_BLK_F_TOPOLOGY because it will just use the VPD data if > the page is long enough. virtio is a bit underspecified, but the > Linux guest driver has the same behaviour as scsi in that respect. Ok, then the right fix is to clarify the spec probably. I've applied the patch to the block branch. This is something for 0.13, too, I suppose? Kevin