From: "Serguei I. Ivantsov" <administrator@svitonline.com>
To: Dave Jones <davej@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re[2]: 2.4.x & Celeron = very slow system
Date: Sun, 19 Aug 2001 18:51:20 +0300 [thread overview]
Message-ID: <80346034.20010819185120@svitonline.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0108191519430.22917-100000@Appserv.suse.de>
In-Reply-To: <Pine.LNX.4.30.0108191519430.22917-100000@Appserv.suse.de>
Hello Dave,
Sunday, August 19, 2001, 4:22:40 PM, you wrote:
DJ> On Sun, 19 Aug 2001, Serguei I. Ivantsov wrote:
>> With 2.4.x kernel my system (Celeron (Coppermine) 850Mhz (100x8.5)
>> 256Mb i810) behaves like slow i386sx.
>>
>> For example, when I extract 25MB gzip file on 2.2.19 kernel - it
>> takes about 12 seconds, but with 2.4.8(9) - 6(!) MINUTES on the SAME
>> system...
>>
>> The only idea is that 2.4.x kernel turns off cache (L1 & L2) on
>> processor (on my cpu). How can I check it? Any ideas?
DJ> No, we don't do any such frobbing of the cache control registers.
DJ> It is enabled in the BIOS right ?
It is enabled in BIOS.
DJ> Another thing that it might be, is if you're using ACPI instead of
DJ> APM, the cpu-idle may be causing the CPU to run slower than usual
DJ> though throttling.
I'd disabled APM support at all when configuring kernel.
DJ> Although, I've not seen this happen to the extent of what you're
DJ> reporting. If you are running with an ACPI kernel, try booting
DJ> with an APM kernel instead to see if it makes a difference.
Maybe there is some software to test which subsystem fails
(cpu,vm,etc)? Is it possible that software from RH7.0 distribution
can't work correctly with new kernel?
--
Best regards,
Serguei mailto:administrator@svitonline.com
next prev parent reply other threads:[~2001-08-19 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-19 13:06 2.4.x & Celeron = very slow system Serguei I. Ivantsov
2001-08-19 13:22 ` Dave Jones
2001-08-19 15:51 ` Serguei I. Ivantsov [this message]
2001-08-19 15:56 ` Re[2]: " Dave Jones
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=80346034.20010819185120@svitonline.com \
--to=administrator@svitonline.com \
--cc=davej@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;
as well as URLs for NNTP newsgroup(s).