3 ms·
An increase of the size of commonly executed code paths could mean two things. First, it could mean that a lot of special casing has accumulated due to lack of
by fauigerzigerk 17y ago
An increase of the size of commonly executed code paths could mean two things. First, it could mean that a lot of special casing has accumulated due to lack of modularisation or cleanup work.
Or it could mean that these cases do in fact have to be considered on that code path every time and that any "outsourcing" to user mode processes would in fact increase the size of the code path.
If it's the former, then the argument that a micro kernel design encourages more fine grained modularisation and leads to fewer special cases is not completely spurious in my opinion.
But all of this is impossible to judge without looking at the code itself.
- tensor 17y agoSaid in a simpler way: either Linux is poorly designed, or that amount of code is necessary for a general purpose kernel. This assumes that someone needs and actively maintains every feature in the code.
- Tuna-Fish 17y ago> either Linux is poorly designed I take offense at the statement "Linux is designed" :) Of course it is not optimal. Nothing else is either. How can we make it better?