Re: kbuild 2.5 is ready for inclusion in the 2.5 kernel

[Richard Gooch]

Paul Mackerras writes:
> But when have you known a kernel hacker to be satisfied with just
> "faster than the previous system", as distinct from "as fast as I can
> reasonably make it go"? ;-)
[...]
> Don't get me wrong, I think it's great to have all the advantages
> that kbuild-2.5 brings.  However, I also think that those seconds
> spent in the startup code will tend to have a disproportionate
> effect on people's perceptions of the new system.  I know you have
> already spent a lot of effort on this, but I want to get in and have
> a look myself to see if I can spot anything that could be improved
> there.

As Keith says, the new code is faster and more robust than the old
code. Given that tracking kernel drift is a significant load on him,
it makes sense to incorporate the new code now. Once it's in, let
people get used to it and then we can look at optimising it, if need
be. Delaying introduction into the kernel tree because it's not 100%
optimised is wasteful.

				Regards,

					Richard....
Permanent: [e-mail]
Current:   [e-mail]