From: Dave Jones <davej@codemonkey.org.uk>
To: Andrew Morton <akpm@digeo.com>
Cc: vasya vasyaev <vasya197@yahoo.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: Machine's high load when HIGHMEM is enabled
Date: Wed, 6 Nov 2002 17:10:42 +0000 [thread overview]
Message-ID: <20021106171042.GA11614@suse.de> (raw)
In-Reply-To: <3DC94885.AD5B8A3B@digeo.com>
On Wed, Nov 06, 2002 at 08:51:17AM -0800, Andrew Morton wrote:
> For some reason your mtrr table was not covering the last 32 megabytes
> of memory. Probably you could also have fixed this by altering the
> mtrr settings. See Documentation/mtrr.txt in the kernel source tree.
I've seen this happen on systems with onboard graphics cards
that share system RAM as video RAM. The end result is that Linux
sees an amount of mem that isn't a power of two.
In extreme cases, the BIOS has done really mad things like
instead of covering the 1GB with 1 MTRR, it splits it into
7 MTRRs covering 512MB,256MB,128MB,64MB,32MB,16MB,8MB.
Icky.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
next prev parent reply other threads:[~2002-11-06 17:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 21:38 Machine's high load when HIGHMEM is enabled Nakajima, Jun
2002-11-06 10:14 ` vasya vasyaev
2002-11-06 16:51 ` Andrew Morton
2002-11-06 17:10 ` Dave Jones [this message]
2002-11-19 9:29 ` vasya vasyaev
2002-11-19 9:40 ` Andrew Morton
2002-11-20 1:03 ` Gerrit Huizenga
2002-11-19 15:35 ` Martin J. Bligh
-- strict thread matches above, loose matches on Subject: below --
2002-11-04 19:49 Nakajima, Jun
2002-11-05 9:08 ` vasya vasyaev
2002-11-05 21:10 ` vasya vasyaev
2002-11-03 14:17 vasya vasyaev
2002-11-03 14:32 ` Brian Gerst
2002-11-03 15:00 ` Jens Axboe
2002-11-04 0:43 ` Denis Vlasenko
2002-11-04 18:54 ` vasya vasyaev
2002-11-04 19:27 ` Andrew Morton
2002-11-05 10:36 ` vasya vasyaev
2002-11-03 15:28 ` Martin J. Bligh
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=20021106171042.GA11614@suse.de \
--to=davej@codemonkey.org.uk \
--cc=akpm@digeo.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vasya197@yahoo.com \
/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