From: Keith Owens <kaos@ocs.com.au>
To: LA Walsh <law@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Power usage Q and parallel make question (separate issues)
Date: Thu, 01 Feb 2001 14:32:07 +1100 [thread overview]
Message-ID: <11659.980998327@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Wed, 31 Jan 2001 19:02:03 -0800." <3A78D1AB.2C2E743B@sgi.com>
On Wed, 31 Jan 2001 19:02:03 -0800,
LA Walsh <law@sgi.com> wrote:
>This seems to serialize the delete, run the mod-installs in parallel, then run the
>depmod when they are done.
It works, until somebody does this
make -j 4 modules modules_install
There is not, and never has been, any interlock between make modules
and make modules_install. If you let modules_install run in parallel
then people will be tempted to issue the incorrect command above
instead of the required separate commands.
make -j 4 modules
make -j 4 modules_install
You gain a few seconds on module_install but leave more room for user
error.
All of this is cleaned up in the 2.5 kbuild system (work in progress).
I have carefully coded the 2.5 kbuild system so it can be used on 2.4
kernels as well. If you don't mind being an earlier adopter, this will
be fixed in a few weeks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-01 3:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 19:44 Power usage Q and parallel make question (separate issues) LA Walsh
2001-02-01 0:32 ` Keith Owens
2001-02-01 3:02 ` LA Walsh
2001-02-01 3:32 ` Keith Owens [this message]
2001-02-01 8:13 ` LA Walsh
2001-02-01 8:24 ` Keith Owens
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=11659.980998327@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=law@sgi.com \
--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 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.