From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Koni <koni@sgn.cornell.edu>, Nick Piggin <piggin@cyberone.com.au>
Cc: Andrew Morton <akpm@osdl.org>, linux-mm@kvack.org
Subject: Re: VM benchmarks
Date: Wed, 04 Feb 2004 07:57:37 -0800 [thread overview]
Message-ID: <31020000.1075910255@[10.10.2.4]> (raw)
In-Reply-To: <1075908453.6795.149.camel@localhost.localdomain>
> It seems to me that increasing -jX doesn't necessarily result in a
> linear increase in load since the kernel build process has all kinds of
> dependencies and source files distributed in different nested
> subdirectories. Thus, it may not be possible for make to spawn X gcc
> instances say unless there are at least X independent files to compile
> in the directory it's working in. Maybe something about kbuild that I
> don't know, I just use make bzImage.
A full -j on the kernel spawns about 1300 processes constantly on a 16-way,
so there's not too much of a problem there. Make sure you do "make vmlinux"
not "make bzImage" though, as the compression phase is all single-threaded.
There's also a pretty much single-threaded linker phase at the end, which
is unavoidable, but on the whole it scales pretty well.
M.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
prev parent reply other threads:[~2004-02-04 15:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-01 23:36 Nick Piggin
2004-02-02 0:08 ` Andrew Morton
2004-02-02 0:11 ` Nick Piggin
2004-02-02 6:31 ` Martin J. Bligh
2004-02-02 7:51 ` Nick Piggin
2004-02-02 16:50 ` Roger Luethi
2004-02-02 23:17 ` Nick Piggin
2004-02-03 23:16 ` Roger Luethi
2004-02-04 0:13 ` Nick Piggin
2004-02-04 15:27 ` Koni
2004-02-04 15:57 ` Martin J. Bligh [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='31020000.1075910255@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=akpm@osdl.org \
--cc=koni@sgn.cornell.edu \
--cc=linux-mm@kvack.org \
--cc=piggin@cyberone.com.au \
/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