James.Smart@xxxxxxxxxx wrote:
As others stated, id is already a tag/label. You should be able to pass whatever id you want to scsi_scan_target, like the FC ID (port_id),
[...]
If the port id changes during run time, what are you to do ?
[...]
This approach only works as long as the transport's id fits within the target id (an int). How would the SAS address(8byte wwn) utilize such a scheme ?
I don't understand exactly what is being discussed here. But if anybody's intention is to extend the concept of target ID to also provide the concept of transport specific, persistent, globally unique identifiers*, then the datatype of target ID needs to be extended accordingly.
Otherwise the LLDs have to implement a mapping between target IDs and these unique identifiers. This mapping does not need to be persistent. Persistent mappings for whatever purpose can and should be implemented in userspace. (This is how it has always been e.g. with SBP-2.)
*) examples of transport specific, persistent, globally unique identifiers: obviously 8 Byte address from SAS, 8 Byte EUI from SBP-2/ IEEE 1394/ ISO/IEC 13213, or maybe 88 bit GUI from ISO/IEC 13213
-- Stefan Richter -=====-=-=-= =--- =-=== http://arcgraph.de/sr/ - : 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
