From: Paul Fulghum <paulkf@microgate.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sam Ravnborg <sam@ravnborg.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: make -j with j <= 4 seems to only load a single CPU core
Date: Tue, 21 Feb 2006 15:42:41 -0600 [thread overview]
Message-ID: <1140558161.9838.8.camel@amdx2.microgate.com> (raw)
In-Reply-To: <9a8748490602211310j344db10evd685149a3c60b1e7@mail.gmail.com>
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
next prev parent reply other threads:[~2006-02-21 21:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 21:02 make -j with j <= 4 seems to only load a single CPU core Jesper Juhl
2006-02-21 21:10 ` Jesper Juhl
2006-02-21 21:42 ` Paul Fulghum [this message]
2006-02-21 21:47 ` Paul Fulghum
2006-02-21 21:51 ` Jesper Juhl
2006-02-21 21:54 ` linux-os (Dick Johnson)
2006-02-21 21:59 ` Jesper Juhl
2006-02-21 22:02 ` Jesper Juhl
2006-02-21 22:15 ` Sam Ravnborg
2006-02-21 22:18 ` Jesper Juhl
2006-02-23 19:44 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1140558161.9838.8.camel@amdx2.microgate.com \
--to=paulkf@microgate.com \
--cc=akpm@osdl.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.