On 04/27/05 10:54, Martin Peschke3 wrote: > Douglas Gilbert wrote > >>It has been stated that the SAS discovery algorithm (i.e. the >>recursive use of SMP) should be implemented once in the SAS >>transport layer so that all SAS LLDs can use it. Putting >>the SAS discovery algorithm in the user space may be >>even more politically correct. > > > Similarly, in the case of Fibre Channel, a common N_Port or > SCSI target device discovery, preferably in user space, seems > to be desirable. This would require some CT and / or ELS > passthrough interface, for example in order to issue queries > to fabric switches. This is exactly what this RFC is all about. Having such a representation of "what is out there", for SAS, in sysfs, you can "address" such devices via their sysfs file, send SMP frames to their ports, etc. BTW, it is possible for a boot device to be on the SAS domain. I think it may be most convenient for discovery (at least a basic one) to be contained in the kernel. Implications are security, reliability, immediate access, etc. 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
