Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: "J.E.J. Bottomley" <James.Bottomley@steeleye.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Mike Anderson <andmike@us.ibm.com>,
	"Adam J. Richter" <adam@yggdrasil.com>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH] get rid of ->detect for upper layer drivers
Date: Thu, 07 Nov 2002 10:50:08 -0500	[thread overview]
Message-ID: <200211071550.gA7Fo9p03079@localhost.localdomain> (raw)
In-Reply-To: Message from Christoph Hellwig <hch@lst.de> of "Thu, 07 Nov 2002 16:39:54 +0100." <20021107163954.B9189@lst.de>

hch@lst.de said:
> Yupp, IMHO we should move to a better interpretation of the driver
> model.  But the question how do we solve the sg issue.  There are two
> ways I could imagine:

There are other nasties waiting in the pipeline.  The one that's been 
bothering me is the SCSI3 Controller Commands (for arrays and the like).  This 
basically adds array controller information to a standard direct-access 
device, but crucially, it has two different (and incompatible with 
direct-access) ways of addressing the array: physical-by real disk and 
logical-by the actual RAID-n unit.

Most of the time a SCC device is an sd device but with a translation in the 
addressing mode.  It makes sense that SCC would somehow filter the sd 
attachment and add a special scc device type just for the controlling node.

By the way, we already have this in the tree: the compaq cpqfc driver does on 
the fly translation for SCC devices into SD at the low level (that's for the 
RA4100 array).

James



  reply	other threads:[~2002-11-07 15:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-07 12:25 [PATCH] get rid of ->detect for upper layer drivers Adam J. Richter
2002-11-07 14:25 ` Mike Anderson
2002-11-07 15:39   ` Christoph Hellwig
2002-11-07 15:50     ` J.E.J. Bottomley [this message]
2002-11-07 15:53       ` Christoph Hellwig
2002-11-07 19:44       ` Patrick Mansfield
2002-11-07 15:36 ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2002-11-07 18:42 Adam J. Richter
2002-11-07 19:02 ` J.E.J. Bottomley
2002-11-07 18:30 Adam J. Richter
2002-11-07 17:47 Adam J. Richter
2002-11-07 18:08 ` J.E.J. Bottomley
2002-11-07 18:56 ` Mike Anderson
     [not found] <200211071532.HAA21625@freya.yggdrasil.com>
2002-11-07 15:42 ` Christoph Hellwig
2002-11-07 16:27 ` Mike Anderson
2002-11-07 16:22 Adam J. Richter
2002-11-07 16:16 Adam J. Richter
2002-11-07  2:49 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=200211071550.gA7Fo9p03079@localhost.localdomain \
    --to=james.bottomley@steeleye.com \
    --cc=adam@yggdrasil.com \
    --cc=andmike@us.ibm.com \
    --cc=hch@lst.de \
    --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