From: Keith Owens <kaos@ocs.com.au>
To: Eric Weigle <ehw@lanl.gov>
Cc: "Linux kernel mailing list (lkml)" <linux-kernel@vger.kernel.org>
Subject: Re: Safety of -j N when building kernels?
Date: Thu, 23 May 2002 09:32:38 +1000 [thread overview]
Message-ID: <344.1022110358@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Wed, 22 May 2002 10:53:20 CST." <20020522165320.GC18059@lanl.gov>
On Wed, 22 May 2002 10:53:20 -0600,
Eric Weigle <ehw@lanl.gov> wrote:
>So are the kernel's current Makefiles really SMP safe -- can one really
>run multiple jobs when building Linux kernels? Any horror stories, or am
>I just paranoid?
make dep is not parallel safe. On some architectures make -jN dep will
generate corrupt data, especially with module symbol versions. You
might get away with it.
It is not safe on any architecture to make -jN *config dep bzImage
modules in one command, you need three separate commands for make -jN
*config, make -jN dep and make -jN bzImage modules. The install step
must also be a separate command.
Building bzImage and modules should be parallel safe, as long as your
machine can take the cpu load and has enough file descriptors.
Sometimes people do not understand makefiles so the odd driver may not
build correctly. aic7xxx around 2.4.19-pre5 was not parallel safe.
Of course, in kbuild 2.5, all of this is parallel safe. make -j
*config install works fine.
prev parent reply other threads:[~2002-05-22 23:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 16:53 Eric Weigle
2002-05-22 17:24 ` William Park
2002-05-22 17:31 ` Fernando [Quatro]
2002-05-22 18:29 ` Samuel Flory
2002-05-22 20:03 ` James Stevenson
2002-05-22 23:32 ` Keith Owens [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=344.1022110358@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=ehw@lanl.gov \
--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®