On 06/10/15 22:56, Hannes Reinecke wrote:
Actually, I've been thinking about this. Currently I'm not sure if
we should fully embrace this route; after all, 'scsilun_to_int' is
meant to be a conversion from the (abstract) LUN number into our
internal representation.
And as it's internal we're free to use whatever we like.
Where we need to fix up things is in reporting; whenever we display
LUN numbers to userspace (printk or sysfs-wise) we probably should
use the appropriate format.
I'll see if I can whip up a printk format for this.
Never liked the '%llu' format for LUNs anyway.
Hello Hannes,
Making how LUNs are displayed dependent on the LUN addressing method
sounds like a good idea to me. One step further would be to ensure that
the format in which LUNs are entered through configfs matches the format
used to display LUNs. This may require to add an additional
configuration parameter in configfs for the LUN addressing format. E.g.
for users who connect an AIX initiator system to LIO it would be much
more convenient to use LUN numbers like 1, 2, 3 instead of the raw LUN
numbers 256, 512, 768.
Thanks,
Bart.
--
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
