From: Andrew Morton <akpm@digeo.com>
To: vasya vasyaev <vasya197@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Machine's high load when HIGHMEM is enabled
Date: Mon, 04 Nov 2002 11:27:52 -0800 [thread overview]
Message-ID: <3DC6CA38.1B027BD7@digeo.com> (raw)
In-Reply-To: 20021104185435.11019.qmail@web20504.mail.yahoo.com
vasya vasyaev wrote:
>
> Hello,
>
> First of all - thanks to these people, who responded
> to my question.
>
> I have some news...
>
> I've tried kernels:
> 2.4.19 - the same result
> 2.5.44 - the same result
> 2.5.45 - the same result
>
> If I take 1 Gb of memory away, then computer works
> much better, faster (something like without enabled
> HIGHMEM at all).
> The same effect takes place if I say mem=1024M while
> physically box has 2Gb of RAM - everything is fine!
> But if I start HIGHMEM enabled kernel on this box (2Gb
> RAM), then it works too slowly...
>
Please ensure that the mtrr driver is enabled in kernel config,
boot with mem=2G and send the output of `cat /proc/mtrr'.
Also, `dmesg | head -120' would be interesting.
next prev parent reply other threads:[~2002-11-04 19:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-03 14:17 Machine's high load when HIGHMEM is enabled 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 [this message]
2002-11-05 10:36 ` vasya vasyaev
2002-11-03 15:28 ` 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-05 21:38 Nakajima, Jun
2002-11-06 10:14 ` vasya vasyaev
2002-11-06 16:51 ` Andrew Morton
2002-11-06 17:10 ` Dave Jones
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
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=3DC6CA38.1B027BD7@digeo.com \
--to=akpm@digeo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.