From: Craig Robinson <craig.robinson@btinternet.com>
To: linux-kernel-owner@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re[2]: 845GE Chipset severe performance problems
Date: Sat, 29 Mar 2003 17:04:57 +0000 [thread overview]
Message-ID: <153495685337.20030329170457@btinternet.com> (raw)
In-Reply-To: <1048949147.6725.3.camel@dhcp22.swansea.linux.org.uk>
Hello Alan,
Many thanks for the reply..
cat /proc/mtrr shows things, but not sure what it SHOULD be...(output
below)
Running 2.5.66 now seems to have speeded up things considerably,
however, I still consider this slow for a 2.4Ghz machine (we have some
2Ghz under alot of load that will still compile things quicker..)
So any suggestions and of course the help you have already provided
are appreciated.
Craig
--
[/usr/src]# cat /proc/mtrr
reg00: base=0x00000000 ( 0MB), size= 256MB: write-back, count=1
reg01: base=0x10000000 ( 256MB), size= 128MB: write-back, count=1
reg02: base=0x18000000 ( 384MB), size= 64MB: write-back, count=1
reg03: base=0x1c000000 ( 448MB), size= 32MB: write-back, count=1
reg04: base=0x1e000000 ( 480MB), size= 16MB: write-back, count=1
reg05: base=0x1f000000 ( 496MB), size= 8MB: write-back, count=1
reg06: base=0xe0000000 (3584MB), size= 64MB: write-combining, count=1
-
Saturday, March 29, 2003, 2:45:48 PM, you wrote:
AC> Check the mtrr ranges. The odd junk bios gets this wrong and leaves
AC> you with parts of main memory uncached. The symptoms you see might
AC> be from that if they are all identical boxes.
AC> Alan
--
Best regards,
Craig mailto:craig.robinson@btinternet.com
next prev parent reply other threads:[~2003-03-29 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-29 13:03 845GE Chipset severe performance problems Craig Robinson
2003-03-29 14:45 ` Alan Cox
2003-03-29 17:04 ` Craig Robinson [this message]
2003-03-30 15:59 ` Re[2]: " Alan Cox
2003-04-01 18:48 ` Rogier Wolff
2003-04-07 15:06 ` H. Peter Anvin
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=153495685337.20030329170457@btinternet.com \
--to=craig.robinson@btinternet.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel-owner@vger.kernel.org \
--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