On Thu, Jun 21, 2007 at 09:40:35PM -0700, Mike Anderson wrote: > James Bottomley <James.Bottomley@xxxxxxxxxxxx> wrote: > > A proposal to display the correct form of the LUN would be useful if you > > wish to make it? ... The problem is really that SAM specifies a > > possible 4 level structure with 4 possible address methods per level. > > > > The well known LUNs should be simple; there are only three: Report Lun, > > Access Controls and Target Log Pages. The rest we really need input on. > > For instance, I could see the vendors wishing us to combine a > > multi-level flat addressing space into a single logical unit number, > > whereas I could see them wanting us to supply some sort of hierarchy for > > the peripheral and logical unit methods of addressing. > > > > Since you're already using 2 level flat addressing, how do you want to > > see that represented? > > James, why would we would not want to display the lun per SAM4 4.6.2 as > suggested by Stefan in a previous comment. I would also agree to display the LUN in sysfs as 64 bit hex number as advised in SAM4. While the SAM describes different formats and addressing schemes, i don't see how this affects the SCSI layer in the kernel. The kernel gets the 64 bit LUNs and uses them as unique ids. 4.6.1 in SAM4 says in the last sentence, that different values for the 64 bits represent different LUNs, so the assumption of the LUNs being unique is guaranteed. My point of view is mainly from the device driver's (zfcp) and user's point of view. It is only that the disk systems i deal with use the 2 level addressing in the LUNs. The user interface of the disk system displays something like: Volume F000 is exported as FCP LUN 40F04000. When the SCSI midlayer uses and exports this value in sysfs, it should be displayed in the same format (hex). I don't know if the multi level scheme is actually used as hierarchy somewhere. If somebody would be interested in using this information, i think a userspace tool could grab the value from sysfs and display the detailed information according to SAM. -- Christof Schmitt - 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
