On Sun, 9 Dec 2001 Andries.Brouwer@cwi.nl wrote:
> [There is more to say, but I have to go, and maybe you and Linus
> can start telling me why this mechanical approach is silly.
Basically you propose to take the current system, replace it with
something without clear memory management ("let it leak") and then
try to fix the resulting mess.
I would rather switch code that uses kdev_t to use of dynamically
allocated structures. Subsystem-by-subsystem. Keeping decent
memory management on every step.
It's _way_ easier than trying to fix leaks and dangling pointers in
the fuzzy code we'd get with your approach. Just look at the fun
Richard has with devfs right now.
It's easier to convert nth piece when you have n-1 done right and nothing
else using the objects in question. Putting the whole thing together
first and the trying to fix it will be a living horror compared to that.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:17 EST