RE: [PATCH 0/2] struct scsi_lun preparation

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

 



--- "Moore, Eric" <Eric.Moore@xxxxxxxx> wrote:
> On Monday, September 11, 2006 1:56 PM, Jeff Garzik wrote: 
> 
> > > A pretty print for the current u32 would be very useful though for
> > > transports dealing with non single level luns (or address 
> > methods other
> > > than zero).
> > 
> > A better subject line would have been "HCIL isolation" I suppose.  I 
> > would like to see increased usage of the accessors already present in 
> > include/scsi/scsi_device.h, which would ease the transition from 
> > hardcoded HCIL struct members to a more flexible addressing method.
> > 
> > Though, FWIW, for LUNs I would certainly like to see u64 rather than 
> > u32.....
> > 
> 
> shouldn't luns be defined as: 
> 
> u8 lun[8] instead of u64?  
> 
> Luben?

Hi Eric,

Yes, you are absolutely correct, LUNs as well as SAS addresses,
are indeed u8[8], for well known reasons.

    Luben

-
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