public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: sferris@acm.org, James.Bottomley@SteelEye.com, mikenc@us.ibm.com,
	michaelc@cs.wisc.edu, willy@debian.org, hch@lst.de,
	surekhap@cisco.com, linux-scsi@vger.kernel.org
Subject: Re: [linux-iscsi-devel] Re: [PATCH RFC] replace ioctl for sysfs take 2
Date: Thu, 09 Sep 2004 10:40:04 +1000	[thread overview]
Message-ID: <413FA664.6050009@torque.net> (raw)
In-Reply-To: <20040908073843.7dbcddb6.rddunlap@osdl.org>

Randy.Dunlap wrote:
> On Wed, 08 Sep 2004 12:33:51 +1000 Douglas Gilbert wrote:
> 
> | Scott M. Ferris wrote:
> | <snip>
> | > 
> | > Should all drivers that currently use one host for each SCSI initiator
> | > device, and a channel for each initiator port on each device, be
> | > modified to use a host for each initiator port?
> | > 
> | > Documentation/scsi/scsi_mid_low_api.txt says that a host corresponds
> | > to a SCSI initiator device.  Could someone change that to say SCSI
> | > initiator port instead, since that seems to be the new goal?
> | 
> | Scott,
> | Yes, I can change that if we all agree. Randy Dunlap asked me some
> | time back to define what was meant by a "linux SCSI host" and that
> | was the best I could come up with at the time.
> 
> Sorry to be dense here, but what is an "initiator port" in this context?
> Is it a physical connector or something else?  A logical connector?
> (whatever that means)

Probably the best place to start is the diagram at
http://www.t10.org under the "Architecture" tab near the
top of the left hand pane. The focus of that diagram is
the Architectural Model (SAM) of which
http://www.t10.org/ftp/t10/drafts/sam3/sam3r13.pdf
is the latest available draft. The transports are
along the bottom of that diagram and the command sets
are along the top.

The concepts of initiator, target, port and delivery
subsystems are defined (abstractly) in SAM-3.
It then falls to the various transports (e.g. FCP,
iSCSI and SPI) to put "meat" on these abstractions
and add some of their own terms (e.g. "logical connector"
from iSCSI). Transports that are not exclusively used
by SCSI command sets (e.g. iSCSI uses IP) come with
their own architectural models and jargon.

SCSI has been around for over 20 years (see wikipedia.org)
and for the first 15 years was synonymous with the "SCSI Parallel
Interface" (SPI) but that is no longer the case. That
change has been very slow getting out to the wider technical
community (as reflected by the SCSI entry in wikipedia.org)

<snip/>

> | 
> | A few related matters:
> | 
> | Steven Fairchild dropped a proposal for SAS storage management
> 
> "dropped" as in dropped (oh, as in deleted) or as in "added", "put",
> or "placed" ?  Seems to be "added"...

Sorry, just sloppy usage. Authors put proposals on that site
for comment.

Doug Gilbert


  parent reply	other threads:[~2004-09-09  0:41 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <413557CB.8010008@cs.wisc.edu>
     [not found] ` <20040901162042.GC26753@null.msp.redhat.com>
2004-09-06 14:32   ` [linux-iscsi-devel] Re: [PATCH RFC] replace ioctl for sysfs take 2 Christoph Hellwig
2004-09-06 16:33     ` Matthew Wilcox
2004-09-06 18:15       ` Mike Christie
2004-09-06 18:54         ` Mike Christie
2004-09-06 22:48           ` Mike Christie
2004-09-06 23:11             ` James Bottomley
2004-09-07  2:46               ` Mike Christie
2004-09-07 15:35                 ` James Bottomley
2004-09-07 19:19                   ` Scott M. Ferris
2004-09-07 20:42                     ` James Bottomley
2004-09-07 21:05                       ` Scott M. Ferris
2004-09-07 21:12                         ` Mike Christie
2004-09-07 21:24                           ` Scott M. Ferris
2004-09-07 21:33                           ` James Bottomley
2004-09-07 21:37                             ` Mike Christie
2004-09-07 22:05                               ` James Bottomley
2004-09-07 22:40                                 ` Mike Christie
2004-09-07 22:57                                   ` Mike Christie
2004-09-08 10:27                                     ` Mike Christie
2004-09-07 23:34                                   ` James Bottomley
2004-09-08  9:19                                     ` Mike Christie
2004-09-08 14:53                                       ` James Bottomley
2004-09-07 21:14                         ` James Bottomley
2004-09-08  2:33                         ` Douglas Gilbert
2004-09-08 14:38                           ` Randy.Dunlap
2004-09-08 18:11                             ` Bryan Henderson
2004-09-09  0:40                             ` Douglas Gilbert [this message]
2004-09-09 15:40                               ` AJ Lewis
2004-09-07 15:24         ` AJ Lewis

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=413FA664.6050009@torque.net \
    --to=dougg@torque.net \
    --cc=James.Bottomley@SteelEye.com \
    --cc=hch@lst.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=mikenc@us.ibm.com \
    --cc=rddunlap@osdl.org \
    --cc=sferris@acm.org \
    --cc=surekhap@cisco.com \
    --cc=willy@debian.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