From: Luben Tuikov <luben_tuikov@adaptec.com>
To: brking@us.ibm.com
Cc: Tom Duffy <tduffy@sun.com>,
Linux-SCSI Mailing List <linux-scsi@vger.kernel.org>,
"Moore, Eric Dean" <Eric.Moore@lsil.com>
Subject: Re: SAS transport class status?
Date: Fri, 29 Jul 2005 10:43:55 -0400 [thread overview]
Message-ID: <42EA40AB.1000105@adaptec.com> (raw)
In-Reply-To: <42EA3451.9010908@us.ibm.com>
On 07/29/05 09:51, Brian King wrote:
> Luben, are you also working on the PHY transport class James mentions in
> his OLS paper, or have you been focusing just on the SAS transport class?
SAS layer. It sits between a SAS LLDD and SCSI Core, and it manages
phy events, ports and port events, domain discovery, device registration
and unregistration with SCSI Core, etc. Devices are registered with their
respective managing layers: SSP port devices with SCSI Core, STP and directly
attached SATA, and SATA Port multiplier (ports) with libata. SMP ports
are driven by the SAS layer (since SMP is strictly a SAS proto).
SAS LLDDs do phy management, OOB, and report phy, port, and HA events
to the SAS layer. SAS LLDDs do not do port management or discovery or
device management (they are just a "transport").
Attributes of all and any entities managed by the SAS layer
and their relationships are portrayed in sysfs in true manner.
They themselves depict the physical world as seen by the SAS
host adapter.
Reference of the internal infrastucture:
SAS 1.1, chapter 4.
Architecture reference:
SAM4r02, chapter 1.3, Figure 2 (same as in SPC), where
"Device specific commands" is SCSI ULDD (sd, st, etc),
"Shared Command Set" is SCSI Core,
"SCSI Protocols" is the SAS layer for SAS HAs,
"Interconnects" is the SCSI LLDD (aic94xx, etc).
Luben
prev parent reply other threads:[~2005-07-29 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 20:27 SAS transport class status? Tom Duffy
2005-07-28 20:41 ` Luben Tuikov
2005-07-29 13:51 ` Brian King
2005-07-29 14:43 ` Luben Tuikov [this message]
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=42EA40AB.1000105@adaptec.com \
--to=luben_tuikov@adaptec.com \
--cc=Eric.Moore@lsil.com \
--cc=brking@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=tduffy@sun.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox