mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: Christian <christiand59@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Odd sched behaviour; It takes 5 threads or more to load 2 CPU cores during kernel build
Date: Tue, 28 Feb 2006 21:48:12 +0100	[thread overview]
Message-ID: <9a8748490602281248p6877478sa17f25dafe019d4e@mail.gmail.com> (raw)
In-Reply-To: <200602282121.11863.christiand59@web.de>

On 2/28/06, Christian <christiand59@web.de> wrote:
> Am Dienstag, 28. Februar 2006 20:59 schrieb Jesper Juhl:
[snip]
> >
> > Do we have a scheduler problem?
> > An io-scheduler problem?
>
> I'm not really into this, but what happens if you simply start 5 different
> kernel-builds in parallel? I think if it makes a difference then this would
> mean that there's something wrong with make and you could eliminate the first
> two possibilities?!
>

Well, no need for 5 kernel builds in that case.
If I clone my source tree and then simply run
 $ make distclean ; make allnoconfig ; nice make
in each directory in two different shells at the same time, then both
cores get fully loaded.


> > Is it "make" that's being difficult?
> > Is it something in the kernels Makefile that causes the build to
> > behave this way?
> > Could it be a bottleneck in my system somewhere?
> >
> > Anyone got a clue?
> >


--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  reply	other threads:[~2006-02-28 20:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-28 19:59 Jesper Juhl
2006-02-28 20:21 ` Christian
2006-02-28 20:48   ` Jesper Juhl [this message]
2006-02-28 23:27 ` Peter Williams

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=9a8748490602281248p6877478sa17f25dafe019d4e@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=christiand59@web.de \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome