On 04/29/05 06:05, Christoph Hellwig wrote:
> Sure, quoting your initial mail:
>
> /----------------------------------------------------------------------
> | 2. Sysfs SAS Domain
> | -------------------
> |
> | Represent everything which "sits out there" in the SAS
> | domain, irrespective of how you connect to it.
> |
> | /sys/bus/sas/
> | /sys/bus/sas/<WWN_ta0>/
> | /sys/bus/sas/<WWN_ta0>/phys/
> |
> | ...
> \----------------------------------------------------------------------
>
> Here you have a global hiearchy. We are not interested in that, though -
> we only care for what's visible from a certain HBA.
True, it is a "global" hierarchy. But visiblity from a single HBA
is also present in /sys/class/sas_ha/... .
>>Overall, since the discovery process gets (internally) a "picture"
>>of the domain out there, it would be appropriate to show this
>>"picture" to the user.
>
> Absolutely.
Ok, so then we want some kind of "global" representation?
Since the discover process (in its attempt to discover topology
errors) would have to know little or less about the "global" outlook.
Luben
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
