James Smart wrote: > How big of a number do you need ? 48 bits ? > We can up to 64bits, but I'd reserve 8bits for a "type" field. > (ugh, sounds like I'm redefining naming authorities...) > > On a side thought - is the mac address really the right thing to > use for a vendor id. Wouldn't you be extracting the vendor id from > the mac address ? > I was looking for a persistent per hba value for some other long reason that we can work around in userspace so I take back that comment. Are you only sending the vendor id to match some vendor specific userspace code with the event? Currently, for iscsi we only send the host no then match the driver, host and some driver or vendor specific code by using the host no and proc_name attr. This is because for software iscsi and iser we do not know the pci device that will be used. For software iscsi it could be a bonded device or multiple devices depending on tables getting updated. What would we use for the vendor id in this case? Is there a null value or some special unused one we can abuse or why do you need the vendor id value if you can look that up in sysfs by just following the host no to the scsi host dir then going to the pci device? - 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
