From: Matthew Wilcox <matthew@wil.cx>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Christoph Hellwig <hch@infradead.org>,
SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: SCSI BLIST_*, sdev_bflags, and scsi_device flags
Date: Fri, 10 Feb 2006 08:30:46 -0700 [thread overview]
Message-ID: <20060210153046.GC12822@parisc-linux.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0602101023390.5093-100000@iolanthe.rowland.org>
On Fri, Feb 10, 2006 at 10:27:21AM -0500, Alan Stern wrote:
> On Fri, 10 Feb 2006, Christoph Hellwig wrote:
> > Do we need per-device blist flags at all? I suspect just having them in
> > the target should be enough.
>
> Some of the blist flags clearly are per-device: BLIST_KEY, BLIST_ISROM,
> BLIST_NOSTARTONADD, BLIST_MS_SKIP_PAGE_08, BLIST_MS_SKIP_PAGE_3F,
> BLIST_USE_10_BYTE_MS, BLIST_MS_192_BYTES_FOR_3F, BLIST_NOT_LOCKABLE,
> BLIST_NO_ULD_ATTACH, BLIST_RETRY_HWERROR. There are a few others I'm not
> certain about.
Why are these clearly per LUN? I agree some of them are debatable,
but most of them indicate a general lack-of-scsi-spec compliance on the
part of the manufacturer and hence apply to the piece of hardware (==
scsi target) rather than just one of the LUNs in it.
next prev parent reply other threads:[~2006-02-10 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 19:55 SCSI BLIST_*, sdev_bflags, and scsi_device flags Alan Stern
2006-02-10 0:17 ` Patrick Mansfield
2006-02-10 3:00 ` Alan Stern
2006-02-10 18:08 ` Patrick Mansfield
2006-02-10 10:36 ` Christoph Hellwig
2006-02-10 15:27 ` Alan Stern
2006-02-10 15:30 ` Matthew Wilcox [this message]
2006-02-10 15:58 ` Alan Stern
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=20060210153046.GC12822@parisc-linux.org \
--to=matthew@wil.cx \
--cc=hch@infradead.org \
--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 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.