From: Keith Owens <kaos@ocs.com.au>
To: "H. J. Lu" <hjl@lucon.org>
Cc: linux kernel <linux-kernel@vger.kernel.org>,
linux ia64 kernel <linux-ia64@vger.kernel.org>
Subject: Re: Does parallel make work for modules?
Date: Tue, 22 Jun 2004 22:27:35 +0000 [thread overview]
Message-ID: <27002.1087943255@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Tue, 22 Jun 2004 15:08:13 MST." <20040622220813.GA306@lucon.org>
In-Reply-To: <20040622220813.GA306@lucon.org>
On Tue, 22 Jun 2004 15:08:13 -0700,
"H. J. Lu" <hjl@lucon.org> wrote:
>When building 2.6.7 on a 4way Linux/ia64, "make -j4 modules" doesn't
>spawn 4 jobs. I got
>
> 5756 pts/0 S 0:00 make -s -j4 modules
> 5868 pts/0 S 0:00 make -f scripts/Makefile.build obj=fs
> 7240 pts/0 S 0:00 make -f scripts/Makefile.build obj=fs/nfs
> 7269 pts/0 S 0:00 /bin/sh -c set -e; ? gcc -Wp,-MD,fs/nfs/.pagelist.o.
> 7270 pts/0 S 0:00 gcc -Wp,-MD,fs/nfs/.pagelist.o.d -nostdinc -iwithprefi
> 7271 pts/0 S 0:00 /usr/gcc-3.4/libexec/gcc/ia64-unknown-linux-gnu/3.4.1/
> 7272 pts/0 R 0:00 as -x -o fs/nfs/pagelist.o -
>
>2.4 kernel module build work fine. Any ideas?
Works for me, GNU Make version 3.79.1 building 2.6.7 on ia64. make -j8
modules gives a pstree of
bash(2475)---make(29483)-+-make(29806)---make(30111)---make(30112)---sh(30113)---gcc(30114)-+-as(30116)
| `-cc1(30115)
`-make(29857)-+-make(29938)---sh(30153)---gcc(30154)-+-as(30156)
| `-cc1(30155)
|-make(30103)-+-sh(30104)---gcc(30105)-+-as(30107)
| | `-cc1(30106)
| `-sh(30146)---gcc(30147)-+-as(30149)
| `-cc1(30148)
`-make(30130)---sh(30131)---gcc(30132)-+-as(30134)
`-cc1(30133)
Not the full blown 8 way that I asked for, but that is an artifact of
using recursive make instead of a single top level Makefile with all
the dependencies.
next prev parent reply other threads:[~2004-06-22 22:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 22:08 Does parallel make work for modules? H. J. Lu
2004-06-22 22:27 ` Keith Owens [this message]
2004-06-22 23:09 ` Jeff Garzik
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=27002.1087943255@ocs3.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=hjl@lucon.org \
--cc=linux-ia64@vger.kernel.org \
--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