I completly agree with you on the slow steps. What we seem to
disagree about is the order of steps..
> Concerning this split - traces of it occur in a very large
> number of places.
Yupp. And getting rid of those one by one is a a good thing
and I'm happy about every single patch you submit to get rid
of one.
> Let me just mention the raw device that
> I did this afternoon. How does one connect a raw device
> with a block device? Using a struct raw_config_request
> from user space. And look
>
> struct raw_config_request
> {
> int raw_minor;
> __u64 block_major;
> __u64 block_minor;
> };
>
> One of the many places that has a built-in major/minor split.
> Basically this split is unimportant. A dev_t is just a cookie.
> But as soon as you start looking at details this split is
> all over the place.
Yes. And my opinion is that we need to sort these issues out
one for one before moving on to make dev_t bigger, not the other
way around.
-
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/