lkml.org 
[lkml]   [2005]   [Sep]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 2.6.13 14/14] sas-class: SCSI Host glue
On 09/11/05 05:38, Christoph Hellwig wrote:
>>Hmm, lets see:
>>I posted today, a _complete_ solution, 1000 years ahead of this
>>"embryonic SAS class" you speak of.
>
>
> They're actually serving different needs. The host-bases SAS code you
> wrote should be layering below my SAS transport class.

Yes, they are completely orthogonal and can co-exist.

> What SPEC do you think a representation of SAS domains in the linux driver
> model just adhere to?

See figure 10, SAS Domain class diagram, in SAS1r09e. It cross-links
you to SAM-3 (you can also use SAM-4).

> There will be more SAS LLDDs that either do more things in firmware like
> LSI Fusion and ones that do things in the Host like the Adaptec one. And
> we need to support both. The best way to do that is to have a small top
> layer that just unifies the SAS domain presentation, and a 'libsas' layer
> below it for host-bases SAS implementations.

It is a _layer_ just like it is in SAM and SPC and SAS.
It is a _layer_ by SCSI design, if you look in SAM.

SAS is not libsas, but a transport _layer_ sitting between
the interconnect (hardware) and SCSI Core (SAM/SPC).

I wish I could do something to convince you, but you have
to convince yourself of this reading SAM and trying
to draw it out (literally) yourself. Try it for
an SPI domain, FC domain and SAS domain, and then you'll
see it.

The sysfs representation is just a perk of the transport
layer, it is owned and operated by the transport layer.

"transport attribute class" is just an _attribute_ class, Christoph.
"transport layer" is a lot more involved. I sincerely hope
you can see this. E.g. domain discovery belongs in the transport
layer. In SPI, LLDDs did it; in MPT the firmware does it.

With SAS, the domain is passive, and the protocol has evolved
enough (due to SAM) to yield to a common transport layer,
where common routines are done, as the SAS code shows.

The _next_ new protocol after SAS, will also adhere to SAM.
It will not happen tomorrow, but it will come around.

The less we invent our own stuff, and the more we adhere
to a spec, the easier we'd support new techonologies, since
they will adhere to SAM.

Luben

P.S. You know when I mentioned "SCSI" above, I did _not_ mean
SCSI-2 or SCSI (Parallel SCSI). I meant SCSI-3 (SAM).




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-09-13 00:03    [W:0.094 / U:2.296 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site