All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Avi Kivity <avi@redhat.com>
Cc: Avishay Traeger1 <AVISHAY@il.ibm.com>,
	kvm@vger.kernel.org, qemu-devel@nongnu.org,
	virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH] virtio spec: add virtio-blk max sectors feature
Date: Tue, 8 Dec 2009 16:18:00 +1030	[thread overview]
Message-ID: <200912081618.00714.rusty@rustcorp.com.au> (raw)
In-Reply-To: <4B178BCE.7030003@redhat.com>

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.

WARNING: multiple messages have this Message-ID (diff)
From: Rusty Russell <rusty@rustcorp.com.au>
To: Avi Kivity <avi@redhat.com>
Cc: Avishay Traeger1 <AVISHAY@il.ibm.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org,
	virtualization <virtualization@lists.linux-foundation.org>
Subject: [Qemu-devel] Re: [PATCH] virtio spec: add virtio-blk max sectors feature
Date: Tue, 8 Dec 2009 16:18:00 +1030	[thread overview]
Message-ID: <200912081618.00714.rusty@rustcorp.com.au> (raw)
In-Reply-To: <4B178BCE.7030003@redhat.com>

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.

  reply	other threads:[~2009-12-08  5:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03  8:42 [PATCH] virtio spec: add virtio-blk max sectors feature Avishay Traeger1
2009-12-03  8:42 ` [Qemu-devel] " Avishay Traeger1
2009-12-03  9:58 ` Avi Kivity
2009-12-03  9:58 ` Avi Kivity
2009-12-03  9:58   ` [Qemu-devel] " Avi Kivity
2009-12-08  5:48   ` Rusty Russell [this message]
2009-12-08  5:48     ` Rusty Russell
2009-12-08  9:44     ` Avishay Traeger1
2009-12-08  9:44     ` Avishay Traeger1
2009-12-08  9:44       ` [Qemu-devel] " Avishay Traeger1
2009-12-08  9:50       ` Avi Kivity
2009-12-08  9:50         ` [Qemu-devel] " Avi Kivity
2009-12-08  9:50       ` Avi Kivity
2009-12-08  5:48   ` Rusty Russell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200912081618.00714.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=AVISHAY@il.ibm.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=virtualization@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.