All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: "Brian D. McGrew" <brian@visionpro.com>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Building the kernel on an SMP box?
Date: Thu, 27 Jul 2006 21:02:00 -0400	[thread overview]
Message-ID: <44C96208.1060609@tmr.com> (raw)
In-Reply-To: <14CFC56C96D8554AA0B8969DB825FEA0012B3898@chicken.machinevisionproducts.com>

Brian D. McGrew wrote:
> Good morning all!
> 
> Currently I'm building my kernels on a Dell PE 1800 3.0GHz.  My dilemma
> is that I build and rebuild the kernel about twenty times a day and even
> though it only takes about 20 minutes, that's rapidly becoming too slow!
> Today it's the 2.6.17 kernel on FC5 that I'm building with.
> 
> I see all these blurbs out there about someone being able to build a
> complete kernel in under a minute or running an SMP build across
> multiple CPUS and/or multiple machines.
> 
> 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???

I can just about make it on 2xXeons at 3.0GHz, HT enabled, 4GB RAM. But 
the new "Core 2 Duo" stuff is tons faster, is dual core but no HT yet, 
has better cache, faster memory bus... costs more. Some big NUMA 
hardware after that,

I will guess the new cheap point is o/c Core 2 Duo 6700, and will finish 
in about 7 min. Patience is a virtue.

-- 
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.

  parent reply	other threads:[~2006-07-28  0:58 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 [this message]
2006-07-28 13:46 ` Andi Kleen
2006-07-29 19:33   ` Bill Davidsen
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=44C96208.1060609@tmr.com \
    --to=davidsen@tmr.com \
    --cc=brian@visionpro.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.