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