Messages in this thread | | | Date | Fri, 18 Jul 2003 01:11:15 +0200 | From | Andries Brouwer <> | Subject | Re: [PATCH] print_dev_t for 2.6.0-test1-mm |
| |
On Thu, Jul 17, 2003 at 03:43:08PM -0700, Joel Becker wrote: > On Fri, Jul 18, 2003 at 12:24:51AM +0200, Andries Brouwer wrote: > > Premise: some filesystems or archives store 32 bits. > > Conclusion: we must be able to handle that. > > This is unrelated to the kernel, unrelated to system calls, > > it is related to <sys/sysmacros.h>. > > How does linux handle that today? IIRC, it ignores the high > 16bits and treats that 32bit number as 8:8. That is what happens today, > for every filesystem, whether it stores 32 or 16 bits. > Why expand that? We can continue to treat 32bit numbers (eg, > from NFSv2) as 16bit numbers.
:-) A surprising question. Why expand that? Because we would like to use more than 16 bits in device numbers.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |