On Thu, Nov 11, 2004 at 12:36:46PM -0500, Tim Kelly wrote:
> I think I understand. Basically, since top only updates every two
> seconds (default), it sees the CPU usage from a 10,000 foot level. The
> thing I don't fully understand is that sometimes I would two or more
> nbmake processes, so it looked to me that to some degree there was some
> parallelization of the build process. I do understand why the compiler
> itself stayed on one CPU during an object file build, though. That would
> be hard to parallelize.

Ah, each subdirectory gets its own nbmake process--e.g., if it was
currently building /usr/src/bin/cat, you'd have one make for /usr/src,
one for /usr/src/bin, and one for /usr/src/bin/cat. However, those
make processes are mostly waiting for their children to finish doing
the real work, so they use very little CPU.
-- 
Name: Dave Huang         |  Mammal, mammal / their names are called /
INet: khym@azeotrope.org |  they raise a paw / the bat, the cat /
FurryMUCK: Dahan         |  dolphin and dog / koala bear and hog -- TMBG
Dahan: Hani G Y+C 29 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F- Q+++ P+ B+ PA+ PL++