All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Mansfield <patmans@us.ibm.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: SCSI BLIST_*, sdev_bflags, and scsi_device flags
Date: Fri, 10 Feb 2006 10:08:01 -0800	[thread overview]
Message-ID: <20060210180801.GA24712@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0602092150430.24417-100000@netrider.rowland.org>

On Thu, Feb 09, 2006 at 10:00:52PM -0500, Alan Stern wrote:
> On Thu, 9 Feb 2006, Patrick Mansfield wrote:

> Which BLIST bits exactly are per-target?  Obviously everything with LUN in
> the name and probably the two INQUIRY flags.  Anything else?

Per other posts and whether the vendor and product can change across LU's
on a given target, they could all be per-target, but we can't assume
that. I didn't audit the BLIST values.

> > IMO store them all in sdev_bflags for now.
> 
> In fact, the sdev_bflags and the starget_bflags can be copies of each
> other (subject to modification by the host adapter driver, of course).  I
> think the accessors should be inline routines, so they can do
> type-checking on the argument (scsi_device vs. scsi_target).

I was thinking that too, but then you have to get values out of the sdev
flags, and don't need starget flags except to pass bflags around during
scan.

So, just use a per sdev flag.

> Do you mind if I don't bother to write setter routines?

I don't care. hch or James?

I think they would only be used by host drivers or transports, as the scan
would set sdev_bflags = scsi_get_device_flags().

-- Patrick Mansfield

  reply	other threads:[~2006-02-10 18:08 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 [this message]
2006-02-10 10:36 ` Christoph Hellwig
2006-02-10 15:27   ` Alan Stern
2006-02-10 15:30     ` Matthew Wilcox
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=20060210180801.GA24712@us.ibm.com \
    --to=patmans@us.ibm.com \
    --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.