On Mon, 31 Mar 2003, bert hubert wrote:
> > If Andries would actually explain, what he wants to do with the larger
> > dev_t, it would be a lot easier to help him, so that we can at least avoid
> > the biggest mistakes.
>
> Can you envision solutions based on 16 bit kdev_t infrastructure?
I know that 16bit is getting small (but with dynamic assignment even
that is still enough for most people), but OTOH I don't understand the
obsession for 64bit. 32bit is more than enough on a 32bit system.
Somehow it sounds that we just have to introduce a huge dev_t and all our
problems are magically solved and I doubt that. If people want to encode
random information into dev_t, then even 64bit will be soon not enough
anymore, so I want to know how people actually want to use that large
dev_t number. Is that really too much to ask?
(Slowly I'm getting the feeling that there is some sort of 64bit dev_t
conspiracy going on here, with the amount of answers I'm (not) getting
here.)
bye, Roman
-
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/