public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian King <brking@us.ibm.com>
To: Martin Peschke3 <MPESCHKE@de.ibm.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] Hidden scsi devices
Date: Thu, 22 Jan 2004 11:07:22 -0600	[thread overview]
Message-ID: <4010034A.3040903@us.ibm.com> (raw)
In-Reply-To: OF8847A70B.4AA684AE-ONC1256E23.00571E7C-C1256E23.0058163C@de.ibm.com

Martin Peschke3 wrote:
> Brian,
> 
> why should a LLDD need to bother about device characteristics?
> I tend to say that it is completely up to upper layer drivers to
> handle such device specialties.
> How does a LLDD know about that r/w protection feature anyway?

Because the device is reported to the LLDD by the adapter as a
specific device type. The adapter creates a configuration table
describing all attached devices that the LLDD must retrieve. In this
configuration table there are several types of devices:

1. Adapter itself.
2. Generic SCSI devices.
3. Logical disk array devices (VSET)
4. Advanced function devices (devices in RAID arrays).

In my situation the only one who knows about this device characteristic
is the LLDD.


-- 
Brian King
eServer Storage I/O
IBM Linux Technology Center


  reply	other threads:[~2004-01-22 17:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-22 15:57 [PATCH] Hidden scsi devices Martin Peschke3
2004-01-22 17:07 ` Brian King [this message]
2004-01-22 17:22   ` James Bottomley
2004-01-22 17:33     ` Brian King
2004-01-22 17:50       ` James Bottomley
2004-01-22 18:42         ` Mike Anderson
2004-01-22 19:43         ` Mike Anderson
2004-01-22 19:46           ` James Bottomley
2004-01-22 20:13             ` Brian King
  -- strict thread matches above, loose matches on Subject: below --
2004-01-22 15:21 Brian King
2004-01-22 15:50 ` Christoph Hellwig

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=4010034A.3040903@us.ibm.com \
    --to=brking@us.ibm.com \
    --cc=MPESCHKE@de.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox