Yes, we could make dev_t's internally be always 32+32, and do the
marshalling at stat() time. That would actually be my preferred approach,
and would solve some of the problems with using "dev_t" as an opaque type
right now (ie it would solve the "discontiguous region" issue.
> Umm, no. You're far to major/minor biased to realized live get a lot
> sipler for use if we don't do any complicated mapping of old dev_t
> to the larger dev_t.
We HAVE to do the mapping somewhere. Old applications only use the lower
16 bits, and that's just something that MUST NOT be broken.
The question is only _where_ (not whether) we do the mapping. Right now we
keep "dev_t" in teh same format as we give back to user space, and thus we
always map into that format internally. But we don't have to: we can have
an internal format that is different from the one we show users.
Linus
-
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/