linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Jones <davej@suse.de>
To: Steven Cole <elenstev@mesatop.com>
Cc: <esr@thyrsus.com>, Aaron Lehmann <aaronl@vitelus.com>,
	Michael Elizabeth Chastain <chastain@cygnus.com>,
	<kbuild-devel@lists.sourceforge.net>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [kbuild-devel] Re: CML2 1.0.0 release announcement
Date: Thu, 12 Apr 2001 15:12:23 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.30.0104121506110.13766-100000@Appserv.suse.de> (raw)
In-Reply-To: <01041206002400.19748@gopnik.dom-duraki>

On Thu, 12 Apr 2001, Steven Cole wrote:

> Excuse me, but this seems to be something of a red herring.
> ...
>  Adding seconds or tens of seconds at this time on 2001 hardware will
> seem very moot by the time 2.5/2.6 is at the point 2.4.x is now.

Adding tens of seconds per build is not acceptable when you're building
a lot of kernels each day.

The beginning of this thread showed a 15 second stall on an Athlon 800,
vs a 1 second startup for the old system. The point now is that
Eric _is_ working on improving the performance. (Which was probably
in another post you missed).

> If you haven't seen my posts here before, I just joined this list last night.

Find a list archive, read the beginning of the thread.

regards,

Dave.


  reply	other threads:[~2001-04-12 13:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-11 20:56 [kbuild-devel] Re: CML2 1.0.0 release announcement Michael Elizabeth Chastain
2001-04-11 21:46 ` esr
2001-04-12  1:01   ` Aaron Lehmann
2001-04-12  1:53     ` esr
2001-04-12 12:07       ` Dave Jones
2001-04-12 12:00         ` Steven Cole
2001-04-12 13:12           ` Dave Jones [this message]
2001-04-12 16:51           ` Horst von Brand
2001-04-12 16:12             ` Steven Cole
2001-04-12 17:59           ` Jochen Striepe
2001-04-11 22:25 ` Alan Cox
2001-04-12  0:40   ` esr

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=Pine.LNX.4.30.0104121506110.13766-100000@Appserv.suse.de \
    --to=davej@suse.de \
    --cc=aaronl@vitelus.com \
    --cc=chastain@cygnus.com \
    --cc=elenstev@mesatop.com \
    --cc=esr@thyrsus.com \
    --cc=kbuild-devel@lists.sourceforge.net \
    --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;
as well as URLs for NNTP newsgroup(s).