From: Sam Ravnborg <sam@ravnborg.org>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-rc1 make -j4 does not run parallel
Date: Sun, 13 Aug 2006 10:08:48 +0200 [thread overview]
Message-ID: <20060813080848.GA7811@mars.ravnborg.org> (raw)
In-Reply-To: <3740.1155437931@ocs10w.ocs.com.au>
On Sun, Aug 13, 2006 at 12:58:51PM +1000, Keith Owens wrote:
> Dual cpu system.
> 'echo $$' reports current id is 4972
> export KBUILD_OUTPUT=../obj
> make -j4
>
> Building a 2.6.17.7 tree, 'LANG= pstree -pl 4972' shows multiple tasks
> running in parallel. Even here it is only running 2 instead of the 4
> that I expect.
>
> bash(4972)---make(7519)---make(7522)-+-make(7721)---make(8198)---make(8513)---sh(8565)---gcc(8566)---gcc(8572)-+-as(8574)
> | `-cc1(8573)
> `-make(8077)---sh(8558)---gcc(8559)---gcc(8569)-+-as(8571)
> `-cc1(8570)
>
> build a 2.6.18-rc1 or later tree, make -j4 does not run parallel. All
> pstree output shows a single branch, like this.
>
> bash(4972)---make(30031)---make(30034)---make(31797)---make(2840)---sh(3678)---gcc(3681)---gcc(3682)---cc1(3683)
>
> Using 'make -j' without a number or 'make -j<n>' where <n> is greater
> than 4 does show parallel build behaviour. Looks like something is
> decrementing -j<n> as you go down the make tree and decrementing it
> enough that it ends up in a serial build.
Thanks. I will try to look into this within a few days - it looks
strange. But you pstree is a great way to see when it happens.
I have been tossing around with an idea to do some of the veru initial
steps in a shell script rather than in make. This should allow us to
bring down the make invocations but this bug needs to be understood
first.
Sam
prev parent reply other threads:[~2006-08-13 8:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-13 2:58 Keith Owens
2006-08-13 8:08 ` Sam Ravnborg [this message]
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=20060813080848.GA7811@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=kaos@ocs.com.au \
--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
all inboxes | Powered by JetHome®