On Mon, 2006-03-27 at 08:20 -0700, Matthew Wilcox wrote:
> So we don't currently save the scsi_lun anywhere. We, er, translate it
> into a 32-bit int, and carry that around. Obviously this is going to
> have to change for things like iSCSI, but this is totally offtopic for
> your patch. So I agree with you, whoever adds the 64-bit LUN support
> gets to patch the ioctl struct too.
Actually, this is precisely the argument for why we don't want such an
ioctl at all. This area is one of the ones there should be significant
changes in for the forseeable future. 32->64 bit LUNs are probably only
the start; then there'll be elimination of the target ID (or replacing
it with a string). If we have this ioctl, every time this area changes,
so now does the user ABI.
Finally, I really don't think we want to encourage anybody in userspace
to rely on a string of internally generated numbers ... that's what
sysfs paths are for, but at least they're simply strings opaque, so we
can change them.
James
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
