From: Rusty Russell <rusty@rustcorp.com.au>
To: Alexey Zaytsev <alexey.zaytsev@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Avishay Traeger <avishay@il.ibm.com>,
linux-kernel@vger.kernel.org, Avi Kivity <avi@redhat.com>
Subject: Re: [PATCH] virtio_blk: add block topology support
Date: Thu, 21 Jul 2011 17:23:01 +0930 [thread overview]
Message-ID: <8762mw2hpe.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CAB9v_DHEieOMYYLr90Yqw_SmMKGKZxdCeOtC0fs-eSuz6ooV+Q@mail.gmail.com>
On Fri, 15 Jul 2011 03:36:42 +0400, Alexey Zaytsev <alexey.zaytsev@gmail.com> wrote:
> On Mon, Feb 1, 2010 at 04:10, Rusty Russell <rusty@rustcorp.com.au> wrote:
> > On Sun, 31 Jan 2010 06:49:10 am Christoph Hellwig wrote:
> >> On Sat, Jan 30, 2010 at 03:29:49PM +1030, Rusty Russell wrote:
> >> > I bow to your expertise on that. My only query is the __u16 for min_io_size; is that likely to restrict us?
> >>
> >> Looks like you caught me there - I wrote the above odd format about the
> >> physical_block exponent, but scsi actually does the min_io and opt_io
> >> size in logical blocks, too. With that in account the u16 as in scsi
> >> is perfectly fine.
> >
> > Thanks, applied.
>
> Ugh, guys. I know it's already applied long ago, but this kind of
> contradicts the virtio specification, doesn't it?
Ugh indeed! The same field is used by two places, as
VIRTIO_BLK_F_SECTOR_MAX never made it into the linux headers.
> VIRTIO_BLK_F_SECTOR_MAX (10) Maximum total sectors in
> an I/O.
The patch made the spec, but as far as I can tell, no implementation.
If that's right, we just remove it from the spec. If it did make it in,
we now have a very ugly case where the layout will have to vary
depending on what options are negotiated.
Once we've resolved this, I'll update the spec...
Thanks,
Rusty.
next prev parent reply other threads:[~2011-07-21 9:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 19:01 [PATCH] virtio_blk: add block topology support Christoph Hellwig
2010-01-30 4:59 ` Rusty Russell
2010-01-30 20:19 ` Christoph Hellwig
2010-02-01 1:10 ` Rusty Russell
2011-07-14 23:36 ` Alexey Zaytsev
2011-07-21 7:53 ` Rusty Russell [this message]
2011-07-29 19:09 ` Alexey Zaytsev
2011-07-30 4:52 ` Rusty Russell
2011-07-31 18:19 ` Christoph Hellwig
2011-08-01 5:22 ` 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=8762mw2hpe.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=alexey.zaytsev@gmail.com \
--cc=avi@redhat.com \
--cc=avishay@il.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox