On Tue, 2006-02-21 at 22:10 +0100, Jesper Juhl wrote:
> I should probably mention that the kernel I'm currently running and
> observing this behaviour with is 2.6.16-rc4-mm1.
...
> > I find this quite strange since anything from 'make -j 2' and up
> > should be able to keep both cores resonably busy, but there seems to
> > be a huge difference between j <= 4 and j > 4.
I've seen the same thing (on Athlon 64x2 64 bit)
but was not sure if it was a problem.
The break point for me seems to be between -j 2 and -j 3
-j 2 = serialized (or the appearance of)
-j 3 = both cores mostly busy
I'm pretty sure with an earlier 2.6 kernel source (but same environment)
I did not see this. I'll start back tracking to earlier kernels
to see if I can identify when this started.
--
Paul Fulghum
Microgate Systems, Ltd
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
