mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Cameron <smcameron@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Mylex/Compaq RAID controller placement in config
Date: Tue, 6 Nov 2001 12:08:15 -0800 (PST)	[thread overview]
Message-ID: <20011106200815.50754.qmail@web12301.mail.yahoo.com> (raw)

Venkatesh Ramamurthy wrote:

> > I know it might seem silly, but as to make things clearer for most
> > users/admins, wouldn't it be better to just call them SCSI controllers, as
> > they all indeed connect SCSI drives to the host?
> 
> Eventhough they connect SCSI Drives, the fact is that they are totally
> different beast from the OS/driver perspective.

Actually, at least in Alan Cox's tree, the cciss driver is BOTH a SCSI driver
and a block driver simultaneously, or can be configured that way anyhow.  That
change was intruduced for the sole purpose of accessing SCSI tape drives via
array controllers.  (nevermind why you'd want to do that, suffice it to say,
some folks want this ability.)  I would consider it mostly a block driver, even
when SCSI tape drive support is compiled in.

In any case, the "drives" (logical volumes) which are presented by the
hardware/firmware and eventually by the driver to the OS do not in general
correspond 1-to-1 with physical SCSI drives.  Even the SCSI busses presented by
the cciss driver with SCSI tape support do not necessarily correspond with
physical SCSI busses, so considering these controllers "SCSI controllers" is
not really accurate, though typically they _contain_ what you can think of as
one or more SCSI controllers as part of the back-end, which the firmware uses
to control SCSI devices,.  Though, in some cases it could be a fibre-channel
back-end instead of SCSI.  In any case, the nature of the back-end is
irrelevant to the driver for purposes of doing i/o to logical volumes.

Incidentally, last time I checked, Linus' tree contained the documentation
portion of the patch which allowed a cciss controller to access SCSI tape
drives (Documentation/cciss.txt) but none of the actual code that implemented
that functionality... :-/  oh well.

-- steve (aka steve.cameron@compaq.com)

__________________________________________________
Do You Yahoo!?
Find a job, post your resume.
http://careers.yahoo.com

             reply	other threads:[~2001-11-06 20:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-06 20:08 Stephen Cameron [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-06 16:01 Dana Lacoste
2001-11-06 16:16 ` Alan Cox
2001-11-06 16:21 ` Richard B. Johnson
2001-11-06 16:44 ` Ricky Beam
2001-11-06 14:22 Roy Sigurd Karlsbakk
2001-11-06 15:15 ` Alan Cox
2001-11-06 15:15   ` Roy Sigurd Karlsbakk
2001-11-06 15:27     ` Arjan van de Ven
2001-11-06 15:35     ` Alan Cox
2001-11-06 16:00     ` Venkatesh Ramamurthy
2001-11-06 16:37     ` Ricky Beam

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=20011106200815.50754.qmail@web12301.mail.yahoo.com \
    --to=smcameron@yahoo.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®