Re: generating a Linux WWN?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jeff Garzik wrote:
> Luben Tuikov wrote:
>> --- Jeff Garzik <jeff@xxxxxxxxxx> wrote:
>>> The admin will have the option to auto-generate a WWN, should they so
>>> desire.
> 
>> What does that mean?  "auto-generate"?  By whom?
> 
> The admin tells the kernel module to auto-generate a WWN, and the kernel
> module happily obliges.
> 
> The generation algorithm is whatever makes people happy.  I would
> probably pick a fixed prefix like 0x6C 0x69 0x63 ("lin"), something that
> doesn't conflict with IEEE org ids for a long time to come.  Then,
> get_random_bytes() or hash some useful machine characteristics for the
> rest of the bytes.
> 
> 
>> What if they don't "auto-generate" (whatever that means)?
> 
> Well, you either have a WWN or you don't :)

Jeff,
It is not quite black and white. As I tried to point
out, when a SAS HBA is run in target mode, there is
a good chance there aren't _enough_ unique SAS addresses
allocated by the manufacturer.

There should be naa-5 addresses for the ports, it is
the target device address and 0 or more lu addresses that
may need to be generated.


Doug Gilbert


-
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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux