All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Grant Grundler <grundler@google.com>, linux-scsi@vger.kernel.org
Subject: Re: READ CAPACITY 16
Date: Thu, 18 Dec 2008 07:08:51 -0700	[thread overview]
Message-ID: <20081218140851.GI19967@parisc-linux.org> (raw)
In-Reply-To: <494A1272.8040008@panasas.com>

On Thu, Dec 18, 2008 at 11:05:54AM +0200, Boaz Harrosh wrote:
> Matthew Wilcox wrote:
> >>> Algorithm B:
> >>>
> >>> Issue RC10
> >>> Issue RC16
> >>>  -> If it succeeds, use its results in preference to those from RC10
> >>>  -> If it fails, carry on with the results from RC10
> >>>  -> If it times out, reset the device, carry on with the results from RC10
> >> I fail to see an effective difference between Algo A and B.
> > 
> > Whether to issue an RC10 before issuing an RC16 or not.  It matches what
> > we currently do better (we currently issue an RC10 and then issue an
> > RC16 if RC10 reports we have 0xffffffff LBAs).
> > 
> 
> Sorry to barge in but I think this is the most practical solution and the one
> to go to T10 with.
> 
> If a (new) device supports RC16 it should return LBAs==0xffffffff for RC10 even
> if it's capacity is smaller, to indicate an RC16 request.

That breaks compatibility with older software that doesn't know that
RC16 exists.

> If LBAs!=0xffffffff and !SCSI_3 then do not risk RC16 unless a white list
> or load parameter.
> 
> Since you are going to T10 with this the white list should be, as you said
> in other mail, zero length.

I don't need to go to T10 for anything except Algorithm D.

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

  reply	other threads:[~2008-12-18 14:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17 16:42 READ CAPACITY 16 Matthew Wilcox
2008-12-17 17:50 ` Grant Grundler
2008-12-17 18:06   ` Matthew Wilcox
2008-12-17 18:57     ` Grant Grundler
2008-12-17 19:04     ` James Bottomley
2008-12-17 19:11       ` Matthew Wilcox
2008-12-17 19:14         ` James Bottomley
2008-12-17 19:32           ` Matthew Wilcox
2008-12-17 19:36             ` James Bottomley
2008-12-17 19:49               ` Matthew Wilcox
2008-12-18  9:05     ` Boaz Harrosh
2008-12-18 14:08       ` Matthew Wilcox [this message]
2008-12-18 14:38         ` Boaz Harrosh
2008-12-18 14:49           ` Matthew Wilcox
2008-12-18 14:52           ` James Bottomley
2008-12-18 14:59             ` Boaz Harrosh
2008-12-18 20:41 ` Douglas Gilbert
  -- strict thread matches above, loose matches on Subject: below --
2008-12-17 17:20 bburk
2008-12-17 17:25 ` Matthew Wilcox
2004-12-09 14:33 read capacity 16 Frank Borich
2004-12-09 15:02 ` Christoph Hellwig
2004-12-08 21:07 Frank Borich

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=20081218140851.GI19967@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=bharrosh@panasas.com \
    --cc=grundler@google.com \
    --cc=linux-scsi@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 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.