public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: ?ric Piel <eric.piel@tremplin-utc.net>,
	linux-scsi@vger.kernel.org,
	Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [PATCH] set CONFIG_SCSI_MULTI_LUN by default and update help
Date: Sun, 3 May 2009 09:24:08 -0600	[thread overview]
Message-ID: <20090503152408.GT8822@parisc-linux.org> (raw)
In-Reply-To: <1241364068.5596.55.camel@mulgrave.int.hansenpartnership.com>

On Sun, May 03, 2009 at 10:21:08AM -0500, James Bottomley wrote:
> On Sun, 2009-05-03 at 09:11 -0600, Matthew Wilcox wrote:
> > On Sun, May 03, 2009 at 09:57:15AM -0500, James Bottomley wrote:
> > > Actually, I'd really rather not alter the default value of this setting.
> > > Multi-lun is rapidly becoming obsolete: any modern devices conforming to
> > > SCSI-3 use REPORT LUNS instead of doing LUN scanning, which gets us out
> > > of the issue.  Conversely, the ancient devices which rely on correctly
> > > setting this are more likely to get upset about any change in the
> > > balance.
> > 
> > Yes, but USB devices are prohibited from being SCSI-3 devices, so it's
> > not becoming obsolete.
> 
> No they're not, there's nothing in the USB specs that say this.  UAS
> will specifically require it.

I didn't mean "prohibited by the USB spec", I meant "prohibited by Linux",
for the exact reason you say below.

> The problem is we don't trust USB manufacturers with standards
> compliance any further than they could spit a rat, so we assume when
> they say they conform to SCSI-3 or above that they must have got it
> wrong and push it back down to SCSI-2.
> 
> Because of this, no-one actually knows how many working SCSI-3 USB
> devices we might have supported.

This is true.  Suggestions for a better way to handle USB devices ... ?

-- 
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:[~2009-05-03 15:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-03 13:57 [PATCH] set CONFIG_SCSI_MULTI_LUN by default and update help Éric Piel
2009-05-03 14:57 ` James Bottomley
2009-05-03 15:08   ` Éric Piel
2009-05-03 15:17     ` James Bottomley
2009-05-03 15:11   ` Matthew Wilcox
2009-05-03 15:21     ` James Bottomley
2009-05-03 15:24       ` Matthew Wilcox [this message]
2009-05-03 18:37         ` Alan Stern
2009-05-04 10:43   ` [PATCH] Update wording of CONFIG_SCSI_MULTI_LUN help Éric Piel

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=20090503152408.GT8822@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=eric.piel@tremplin-utc.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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