On Fri, 1 Aug 2008, Jochen Schulz wrote: > Andrew Sackville-West: > > > > [...] Maybe you could just run multiple kernel compiles > > simultaneously, including one or two that are reading/writing to a > > network share and see what happens that way? > > To use all cores available when compiling a kernel, you don't need to > run several compilation jobs at the same time. Just set > CONCURRENCY_LEVEL to the number of cores you have.
I looks like both CPUs are doing their thing on the kernel compile. Here is a quick look at the top info: top - 11:56:30 up 4 days, 3:17, 3 users, load average: 1.15, 1.19, 0.85 Tasks: 80 total, 2 running, 78 sleeping, 0 stopped, 0 zombie Cpu0 : 46.9%us, 3.9%sy, 0.0%ni, 46.6%id, 2.6%wa, 0.0%hi, 0.0%si, 0.0%st Cpu1 : 41.7%us, 5.8%sy, 0.0%ni, 52.1%id, 0.0%wa, 0.0%hi, 0.3%si, 0.0%st Mem: 3927348k total, 3706124k used, 221224k free, 263100k buffers Swap: 5076532k total, 0k used, 5076532k free, 2570492k cached Thanks, Ken -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]