All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
To: Valdis.Kletnieks@vt.edu
Cc: john weber <weber@sixbit.org>, linux-kernel@vger.kernel.org
Subject: Re: Performance Tuning
Date: Thu, 20 May 2004 18:49:48 +0200	[thread overview]
Message-ID: <40ACE1AC.3000803@gmx.de> (raw)
In-Reply-To: <200405201642.i4KGgDgJ000683@turing-police.cc.vt.edu>

Valdis.Kletnieks@vt.edu wrote:
> On Thu, 20 May 2004 12:05:15 -0000, john weber <weber@sixbit.org>  said:
> 
> 
>>Kernel compiles take 6m38s on my P4 2.8GHz (with HT enabled) and 
>>512 MB RAM as compared to 20-30 seconds reported by folks online. 
>>I am running kernel 2.6.6.
[snip]
> Seriously - the only way to do a kernel build in 20 seconds is to use 'make
> -j20' or so, and have enough processors to handle it, and enough RAM so that
> you can basically do the whole thing in the fin-core cache rather than beating
> on the disk....

20sec sounds very far from reality for me. I have athlon xp@2.2GHz and 
with gcc3.4 it takes about 4min to compile a 2.6.6-mm kernel. Using 
gcc3.3.x it needs minutes more.

Prakash

  reply	other threads:[~2004-05-21 23:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-20 12:05 Performance Tuning john weber
2004-05-20 13:00 ` Richard B. Johnson
2004-05-20 16:42 ` Valdis.Kletnieks
2004-05-20 16:49   ` Prakash K. Cheemplavam [this message]
2004-05-20 18:39 ` cliff white
2004-05-20 18:51 ` Tim Bird
2004-05-21 14:56 ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2005-08-29  5:17 How can execute .cpp program with gcc command kranthi
2005-08-30  4:46 ` Performance tuning Vikas
2002-07-10 15:15 David Dougall
2002-07-10 21:04 ` Tom McNeal
2002-07-10 21:17   ` Trond Myklebust

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=40ACE1AC.3000803@gmx.de \
    --to=prakashkc@gmx.de \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=weber@sixbit.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.