mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <ak@muc.de>
Cc: "Martin MOKREJ©" <mmokrejs@ribosome.natur.cuni.cz>,
	linux-kernel@vger.kernel.org
Subject: Re: memory management weirdness
Date: Tue, 22 Feb 2005 09:04:31 +0100	[thread overview]
Message-ID: <20050222080431.GB778@elte.hu> (raw)
In-Reply-To: <m14qg5mq5v.fsf@muc.de>


* Andi Kleen <ak@muc.de> wrote:

> >   Although I've not re-tested this today again, it used to help a bit to specify
> > mem=3548M to decrease memory used by linux (tested with AGP card plugged in, when
> > bios reported 3556MB RAM only).
> >
> >   I found that removing the AGP based videoc card and using an old PCI based
> > video card results in bios detecting 4072MB of RAM. But still, the machine was
> > slow. I've tried to "cat >| /proc/mtrr" to alter the memory settings, but the
> > result was only a partial speedup.
> >
> >   I'm not sure how to convince linux kernel to run fast again.
> 
> It's most likely a MTRR problem. Play more with them.

in particular, try to create two small tables in the same format: one
showing the e820 memory map as reported in your kernel log, and one
showing the mtrr areas. If there is any e820 area that is not write-back
cached via the mtrr mappings then that's the problem. You can also use
"mem=exactmap,..." to fix up the memory map that the BIOS provides to
Linux. Slowdowns are very often such MTRR problems. (perhaps the kernel
should report RAM areas that are not covered by MTRR write-back?)

	Ingo

  reply	other threads:[~2005-02-22  8:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-21 13:46 Martin MOKREJŠ
2005-02-21 23:47 ` Andi Kleen
2005-02-22  8:04   ` Ingo Molnar [this message]
2005-02-22 10:14     ` Martin MOKREJŠ
2005-06-02 11:31   ` Martin MOKREJS(
2005-02-21 14:20 Parag Warudkar
2005-02-22  9:57 ` Martin MOKREJŠ
2005-02-24  2:24   ` Parag Warudkar

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=20050222080431.GB778@elte.hu \
    --to=mingo@elte.hu \
    --cc=ak@muc.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmokrejs@ribosome.natur.cuni.cz \
    /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®