Re: More on bigger kdev_t
Zack Weinberg (zack@bitmover.com)
Sat, 09 Oct 1999 15:55:01 -0700
Andi Kleen wrote:
> alan@lxorguk.ukuu.org.uk (Alan Cox) writes:
>
> > > If kdev_t is a 4 byte long structure, (i.e., using a 16/16 major/minor
> > > split), the compiler should be able to do a relatively good job of
> > > optimizing accesses to it. If not, that's a compiler bug that we should
> > > report, and ask the gcc/egcs folks to fix.
> >
> > On many platforms
> >
> > struct
> > {
> > u16 a;
> > u16 b;
> > };
> >
> > is an 8 byte object.
>
> But
>
> struct bla {
> unsigned a : 16;
> unsigned b : 16;
> };
>
> isn't (and has the same type checking benefits)
User space is already carrying around 64-bit dev_t. Let's make the
kernelside type match: 32 bit minor and major both.
zw
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/