--- Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx> wrote:
> Luben Tuikov wrote:
> > 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.
True, true.
But those subsystems are shielded from SCSI Core. Plus SCSI Core
is managed by people unaware of SAM or the layering infrastructure.
Luben
> > 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
