Roman,
There are a couple things being discussed here. One is the size
of dev_t. The other is dynamic numbers. It would seem that most folks
agree with a larger dev_t and a more dynamic numbering system. Let's
assume we want both for now (folks who don't, please keep out for a
second). There are three courses of action that seem to be advocated.
1) Ship 2.6 with 16bit dev_t, work on a larger dev_t and perfect dynamic
devices in 2.7.
2) Ship 2.6 with a (32|64)bit dev_t, work on a perfect dynamic scheme in
2.7.
3) Hold 2.6 until it can ship with (32|64)bit dev_t and perfect dynamic
devices.
Many folks, Peter and myself included, are claiming that choice
(1) is absolutely untenable. We need more device space today, not in 3
years when 2.7 becomes 2.8.
If I understand you correctly (and here is why I mailed), you
feel that choice (2) is the worst of the choices. You feel that we
should either choose course (1) or course (3). I'm not sure which of
those you prefer.
Joel
--Life's Little Instruction Book #335
"Every so often, push your luck."
Joel Becker Senior Member of Technical Staff Oracle Corporation E-mail: joel.becker@oracle.com Phone: (650) 506-8127 - 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/