Yes. kbuild 2.4 invokes a separate copy of make for each directory,
with significant start up overhead. Plus it runs most directories
twice, once for built in and once for modules, it was the only way to
handle separate flags for kernel and module code. Rules.make has been
trying to use make as a programming language, but it was never designed
kbuild 2.5 does a lot of work up front (in C) to build a single, global
makefile which only requires one copy of make and one pass over the
entire kernel. When the global makefile has been built and the kernel
is already up to date, make runs the global makefile with the entire
kernel dependency tree in sub second time.
BTW, all kbuild 2.5 times so far have been using the unoptimized
pre-processor programs, with all my debugging checks still turned on.
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/