From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rusty Russell Subject: Re: [PATCH] virtio spec: add virtio-blk max sectors feature Date: Tue, 8 Dec 2009 16:18:00 +1030 Message-ID: <200912081618.00714.rusty@rustcorp.com.au> References: <4B178BCE.7030003@redhat.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: Avishay Traeger1 , kvm@vger.kernel.org, qemu-devel@nongnu.org, virtualization To: Avi Kivity Return-path: Received: from ozlabs.org ([203.10.76.45]:53055 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752583AbZLHFr5 (ORCPT ); Tue, 8 Dec 2009 00:47:57 -0500 In-Reply-To: <4B178BCE.7030003@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Thu, 3 Dec 2009 08:28:38 pm Avi Kivity wrote: > On 12/03/2009 10:42 AM, Avishay Traeger1 wrote: > > I previously submitted a patch to have the guest virtio-blk driver get the > > value for the maximum I/O size from the host bdrv, rather than assume that > > there is no limit. Avi requested that I first patch the virtio spec > > (http://ozlabs.org/~rusty/virtio-spec/). Below is that patch. > > > > Please CC me on replies, as I am not subscribed. > > > > > > Copying Rusty and virtualization@. Thanks Avi... Avishay; this would be the total sectors in an I/O, as separate from SIZE_MAX (maximum size of any single scatterlist entry) and SEG_MAX (maximum number of scatterlist entries)? Seems like a reasonable idea; esp if you need it. Thanks! Rusty. From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NHsvq-0003xb-Vr for qemu-devel@nongnu.org; Tue, 08 Dec 2009 00:48:19 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NHsvj-0003w5-4D for qemu-devel@nongnu.org; Tue, 08 Dec 2009 00:48:15 -0500 Received: from [199.232.76.173] (port=57803 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NHsvi-0003vz-QI for qemu-devel@nongnu.org; Tue, 08 Dec 2009 00:48:10 -0500 Received: from ozlabs.org ([203.10.76.45]:54960) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NHsvi-0001Gr-5e for qemu-devel@nongnu.org; Tue, 08 Dec 2009 00:48:10 -0500 From: Rusty Russell Date: Tue, 8 Dec 2009 16:18:00 +1030 References: <4B178BCE.7030003@redhat.com> In-Reply-To: <4B178BCE.7030003@redhat.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200912081618.00714.rusty@rustcorp.com.au> Subject: [Qemu-devel] Re: [PATCH] virtio spec: add virtio-blk max sectors feature List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Avishay Traeger1 , qemu-devel@nongnu.org, kvm@vger.kernel.org, virtualization On Thu, 3 Dec 2009 08:28:38 pm Avi Kivity wrote: > On 12/03/2009 10:42 AM, Avishay Traeger1 wrote: > > I previously submitted a patch to have the guest virtio-blk driver get the > > value for the maximum I/O size from the host bdrv, rather than assume that > > there is no limit. Avi requested that I first patch the virtio spec > > (http://ozlabs.org/~rusty/virtio-spec/). Below is that patch. > > > > Please CC me on replies, as I am not subscribed. > > > > > > Copying Rusty and virtualization@. Thanks Avi... Avishay; this would be the total sectors in an I/O, as separate from SIZE_MAX (maximum size of any single scatterlist entry) and SEG_MAX (maximum number of scatterlist entries)? Seems like a reasonable idea; esp if you need it. Thanks! Rusty.