From: James Bottomley <jejb@steeleye.com>
To: Luben Tuikov <luben_tuikov@adaptec.com>
Cc: Christoph Hellwig <hch@lst.de>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] allow a transport to pre-initialize starget_data
Date: Mon, 15 Aug 2005 10:53:54 -0500 [thread overview]
Message-ID: <1124121234.5089.14.camel@mulgrave> (raw)
In-Reply-To: <4300B7C4.8060400@adaptec.com>
On Mon, 2005-08-15 at 11:41 -0400, Luben Tuikov wrote:
> Hmm, you've
> "found an actual use for channel (exposing underlying physical discs
> of raid devices)".
>
> I'm completely befuddled James.
For RAID cards in the SCSI subsystem that export RAID devices as SCSI
devices, there's a need of a standard way to get at the underlying
devices (for DV, parameter setting or configuration). The idea is to
expose these devices on a non zero channel.
> What if we didn't have "channel" (SPI leftover) in the first place?
> Or, if an LU is implemented as a RAID device, how do you find out its
> individual disks?
It's not a SPI leftover. It's used by HBA's that have two channels that
genuinely share resources. Although most modern SCSI cards simply have
two chips (and hence two separate HBAs) per channel, there are a few, of
which the qlogic fc card is one, that still have this one chip per two
channels model.
> Is there a spec or standard that you're following in doing this?
It's an OS abstraction, so no.
James
next prev parent reply other threads:[~2005-08-15 15:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 13:42 [PATCH] allow a transport to pre-initialize starget_data Christoph Hellwig
2005-08-15 15:14 ` James Bottomley
2005-08-15 15:18 ` Luben Tuikov
2005-08-15 15:23 ` James Bottomley
2005-08-15 15:41 ` Luben Tuikov
2005-08-15 15:53 ` James Bottomley [this message]
2005-08-15 16:10 ` Luben Tuikov
2005-08-15 16:32 ` James Bottomley
2005-08-15 16:40 ` Luben Tuikov
2005-08-15 15:25 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2005-08-18 14:17 James.Smart
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=1124121234.5089.14.camel@mulgrave \
--to=jejb@steeleye.com \
--cc=hch@lst.de \
--cc=linux-scsi@vger.kernel.org \
--cc=luben_tuikov@adaptec.com \
/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.