From: Matt Hahnfeld <matth@everysoft.com>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SLOW machine when HIGHMEM enabled (1gb memory, kernel 2.4.22)
Date: Sun, 21 Sep 2003 17:07:58 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0309211657470.12232-100000@sotec> (raw)
In-Reply-To: <16238.2932.99763.591328@gargle.gargle.HOWL>
Mikael --
Thanks for the help!
I have posted my /proc/mtrr and /proc/meminfo to
http://www.layover.com/matt/kernel/ .
The "lowmem" ones are when HIGHMEM was disabled, the "highmem" ones are
2.4.22 with CONF_HIGHMEM4G. /proc/mtrr looks exatly the same whether or
not highmem is enabled.
I have the newest stable bios from Asus as of yesterday.
What should I see if the high memory isn't cachable?
On Sun, 21 Sep 2003, Mikael Pettersson wrote:
> Matt Hahnfeld writes:
> > I have an ASUS P4P800-VM motherboard with 2 sticks of 512mb PC3200 and
> > a single 2.4 ghz P4 processor. The kernel is vanilla 2.4.22 configured
> > for SMP (hyperthreading).
> >
> > When I use a kernel with high memory support off, I get good
> > performance (despite not being able to use some of my memory). When I
> > enable CONFIG_HIGHMEM4G the remaining memory is detected, but the
> > machine takes a big performance hit and starts running very slow --
> > ie. kernel compilation looks like it would take 5 days instead of 5
> > minutes. /proc/meminfo doesn't look particularly strange and no
> > strange log messages show up -- everything just runs slow...
> >
> > CONFIG_HIGHMEM64G produces the same results...
> >
> > Any suggestions?
>
> Sounds like maybe the high RAM isn't cacheable.
> What does /proc/mtrr and dmesg look like?
>
> Have you verified that you're running the latest BIOS?
>
next prev parent reply other threads:[~2003-09-21 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-21 20:10 Matt Hahnfeld
2003-09-21 20:35 ` Mikael Pettersson
2003-09-21 21:07 ` Matt Hahnfeld [this message]
2003-09-21 21:42 ` Mikael Pettersson
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.44.0309211657470.12232-100000@sotec \
--to=matth@everysoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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®