From: Bill Davidsen <davidsen@tmr.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Building the kernel on an SMP box?
Date: Sat, 29 Jul 2006 15:33:09 -0400 [thread overview]
Message-ID: <44CBB7F5.1080704@tmr.com> (raw)
In-Reply-To: <p73wt9x4zay.fsf@verdi.suse.de>
Andi Kleen wrote:
> "Brian D. McGrew" <brian@visionpro.com> writes:
>> So, to ask the group that should know the best ... What would be a
>> reasonable configuration to get my builds down under five minutes or so?
>> And then to go to the extreme, what kind of horsepower should I be
>> looking for if I want get the build times down to say a minute or so???
>
> Depending on your build pattern you can likely speed up rebuilds by
> using ccache.
>
> If that doesn't help get one or two (or more as needed) cheap dual
> core systems and use icecream (http://en.opensuse.org/Icecream) to do
> a cluster build and build with -jN (N=2*available cores/threads or so)
That sounds really useful, although I bet it assumes that the build
environment is the same on all machines. Or at least similar. I'll have
to try that, I have two lightly used machines to add to the build. Thanks!
--
Bill Davidsen <davidsen@tmr.com>
Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.
next prev parent reply other threads:[~2006-07-29 19:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 14:06 Building the kernel on an SMP box? Brian D. McGrew
2006-07-27 15:19 ` Rolf Eike Beer
2006-07-28 1:02 ` Bill Davidsen
2006-07-28 13:46 ` Andi Kleen
2006-07-29 19:33 ` Bill Davidsen [this message]
2006-07-29 19:29 ` Andi Kleen
2006-07-29 21:30 ` Bill Davidsen
2006-07-30 16:18 ` Valdis.Kletnieks
2006-07-30 17:11 ` Andi Kleen
2006-07-29 14:29 ` Jesper Juhl
2006-07-29 18:54 ` Handle X
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=44CBB7F5.1080704@tmr.com \
--to=davidsen@tmr.com \
--cc=ak@suse.de \
--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