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
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
