Luben Tuikov wrote:
On 09/28/05 18:43, Andre Hedrick wrote:
Have you and company considered the approach of mapping to a library of
sorts?
Hmm, it is not a library.
It is a layer, again, because of what the chip actually is, and because
of what it implements.
Take a look at the announcement text, I do give some description there
and in the code the drivers/scsi/sas-class/README file describes
the event/managment infrastructure. Also you can take a look at the code.
http://linux.adaptec.com/sas/
What you'll see in the code is:
hardware implementation (interconnect, SAM 4.15, 1.3)
firmware implementation (interconnect, SDS, SAM 4.6, 1.3)
LLDD (SAM, section 5, 6, 7)
Transport Layer (SAM 4.15, SAS)
SCSI Core (SAM section 4,5,8)
Commmand Sets (SAM section 1)
A very nice explanation in latest SAM4r03,
section 4.15 The SCSI model for distributed communications.
BTW, Linux' implementations of transports like USB storage and SBP-2
have always been similarly layered. (Actually they come with at least
one more layer between LLDD and SCSI core.) Needless to say that these
transports need their specific managing infrastructures. So this
layering is not at all new to Linux.
Now for MPT based solutions you have:
LLDD (SAM, section 5, 6, 7)
SCSI Core (SAM section 4,5,8)
Commmand Sets (SAM section 1)
You see? No Transport Layer between LLDD and SCSI Core!
Why? Because all this work is done in FIRMWARE!
--
Stefan Richter
-=====-=-=-= =--= ===-=
http://arcgraph.de/sr/
-
: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
