--- Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx> wrote: > Do all these transports use the same *name* for the attribute holding > the target port identifier's? Sure, it is "tpid". > In other words, is userspace able to find > the target port identifier without knowing which transport is at work? How can that be? The target port identifier is by definition a transport property? "Userspace" which you have in mind will be more interested in the device name and other ID properties as returned by the INQUIRY facilities. Some are transport specific some are not. Either way userspace can follow a pointer from the sysfs device entry to the transport, just as sg-utils and lsscsi does now for the SAS Stack (my version of it at least). > Regarding the TPID: The /how/ should be left to the transport layer > implementation; but the /where/ should be uniform in all transports. This maybe hard to do since the structure of the domain is different for different protocols. Of course this can be hacked by using symlinks... Luben - To unsubscribe from this list: 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
