On 04/25/05 12:14, Christoph Hellwig wrote:
> Please read the previous mail again, you're not getting it at all.
> If you don't understand the problems it's not worth talking about more.
Here is your original email:
On 04/24/05 07:19, Christoph Hellwig wrote:
> This is contrary to any sysfs topology I know about, especially any
> existing transport class (SPI, FC, iSCSI). We only ever care about
> what's seen from a HA, e.g. if you have muliple SPI cards that are
> on a single parallel bus you'll have the same bus represented twice,
> similarly if you have two fibre channel HBAs connected to the same
> SAN you'll have the SAN topology duplicated in both sub-topologies.
> This matches the internal data structure of the scsi subsystem and
> the transport class, e.g. we have a scsi_device object for every lun
> that's seen from a hba, linked to the HBAs Scsi_Host object and not
> one shared by multiple HBAs. Dito for fibre channel remote ports.
You're are stating that:
1) You "only ever care about what's seen from a HA",
2) "if you have muliple SPI cards that are on a single parallel
bus you'll have the same bus represented twice"
3) "we have a scsi_device object for every lun
that's seen from a hba, linked to the HBAs Scsi_Host object
and not one shared by multiple HBAs"
So in effect, you _want_ duplication, right? This is perfectly OK.
In fact it is desirable (and has never been under question).
This isn't directly related to the RFC. The RFC basically
outlines the result of *a SAS discovery process*. The discovery
process/LLDD can register the LU many times. This has *never* been an
issue of discussion.
Your concern is satisfied in that, /sys/bus/scsi/devices/... would
point to the LU. And a link from /sys/class/sas_ha/ha0/devices/
to the LU could be placed (outside the scope of this RFC). The RFC
doesn't mention LUs, but they could be included if you wish so.
Luben
-
: 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
