mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Morris <jmorris@intercode.com.au>
To: Kirk Reiser <kirk@braille.uwo.ca>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.xx kernels won't run on my Athlon boxes
Date: Sat, 7 Sep 2002 01:18:03 +1000 (EST)	[thread overview]
Message-ID: <Mutt.LNX.4.44.0209070106200.10905-100000@blackbird.intercode.com.au> (raw)
In-Reply-To: <x765xj9wgg.fsf@speech.braille.uwo.ca>

On 6 Sep 2002, Kirk Reiser wrote:

> I can't be the only person experiencing this.

I'm not sure if this is related, but I've noticed a major performance
issue starting in 2.5.32 (and still present in .33) on a dual celeron
system that has otherwise been working fine for a couple of years with all
kinds of bleeding edge kenels.  Some initial profiling output is showing
up to a factor of 10x the number of clock ticks and load for kernel
compiles and local copying of kernel trees.  hdparm -t is showing a 25%
decrease in throughput.  This is an IDE system with a PIIX4 controller.

If time permits, I'll do some more investigation.

- James
-- 
James Morris
<jmorris@intercode.com.au>




  parent reply	other threads:[~2002-09-06 15:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-05 23:53 Hell.Surfers
2002-09-06  0:40 ` Alan Cox
2002-09-06 11:41   ` Kirk Reiser
2002-09-06 12:26     ` Alan Cox
2002-09-06 12:40       ` Kirk Reiser
2002-09-06 15:18     ` James Morris [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-06  0:55 Hell.Surfers
2002-09-06 11:51 ` Kirk Reiser
2002-09-05 22:56 Hell.Surfers
2002-09-05 23:12 ` 2.5.xx " Kirk Reiser
2002-09-05 19:35 blocksize limitations in scsi tape driver (st) when used with DLT1 tape drives? Friedrich Lobenstock
2002-09-05 20:14 ` 2.5.xx kernels won't run on my Athlon boxes Kirk Reiser

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=Mutt.LNX.4.44.0209070106200.10905-100000@blackbird.intercode.com.au \
    --to=jmorris@intercode.com.au \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=kirk@braille.uwo.ca \
    --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

all inboxes | Powered by JetHome®