Serial Attached SCSI, An Architecture For Linux

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



            Me, early Jan'06: Paper submitted.
Linuxsymposium, 16 Feb 2006 : Paper approved.
Linuxsymposium, date unknown: Silently moved to a BOF, I was never notified.
            Me,  9 Mar 2006 : BOF rejected by me because last year I did held a SAS BOF.
Linuxsymposium,  9 Mar 2006 : moved back to a paper.
Linuxsymposium,  9 Mar 2006 : paper rejected.

Serial Attached SCSI, An Architecture For Linux
https://www.linuxsymposium.org/2006/view_proposal.php?hide_vote=1&content_key=2
---------------------------------
This paper would start with an overview of SCSI (SCSI-3, that is), its
object oriented nature and why such is the direction of SCSI.

Then an introduction to SAS from this SCSI point of view will be given,
i.e. where it fits in the object oriented model, why and how. There may be
very little SAS technical introduction--a couple of sentences, something
anyone would understand and something sufficient for the latter sections of
the paper.

Then an introduction to SAS as an architecture in a SCSI stack would
follow. A layered, object oriented model will be presented, similar to the
one found in my code.

This will be accompanied with a SCSI "architectural roadmap", the how and
why the architecture.

Then an overview of pure-SCSI drivers would be given (at this point the
paper talks about implementations at each layer of the software
stack). Those are implementations which hide the transport layer completely
in their firmware, and present a pure SCSI "picture", a la SAM, to the
OS. How and why they do it.

Then the paper would talk about what unifies those implementations, how it
can be done, and why it should be done this way. An introduction to SDI,
SCSI Driver Interface, would be presented. Why SDI makes sense and how it
can be done for a SCSI stack architecture in an object oriented way. Who
registers it, what they implement, how and why.

There would be a section on a SCSI/ATA Translation, SAT, and a SAT
Layer. Where it fits, how and why. What its interface is and why.

The paper would include pictures and figures as necessary to show layers,
object oriented concepts and the like.
----------------------------------------

-
: 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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux