From: Simon Oliver <simon.oliver@umist.ac.uk>
To: "E. Robert Bogusta" <rob23@tmr.com>
Cc: linux-smp@vger.kernel.org, SuSE Linux List <suse-linux-e@suse.com>
Subject: Re: Kernel Compilation for Dual Xeon system
Date: Wed, 03 Jul 2002 09:12:59 +0100 [thread overview]
Message-ID: <afubs4$jdd$2@main.gmane.org> (raw)
In-Reply-To: Pine.LNX.3.96.1020702133928.28521A-100000@gatekeeper.tmr.com
Rob, thanks again.
Here's what the Kernel help system says on selecting "User address space
size":
Typically there will 128 megabytes less "user memory" mapped
than the number in the configuration option. Saying that
another way, "high memory" will usually start 128 megabytes
lower than the configuration option.
Selecting "05GB" results in a "3.5GB/0.5GB" kernel/user split:
On a system with 1 gigabyte of physical memory, you may get 384
megabytes of "user memory" and 640 megabytes of "high memory"
with this selection.
Why would I want that?
What is the advantage of having a high ratio of "high memory"?
What is this "high memory" used for, the kernel and drivers?
How do I gauge how much high memory I need?
Selecting "1GB" results in a "3GB/1GB" kernel/user split:
On a system with 1 gigabyte of memory, you may get 896 MB of
"user memory" and 128 megabytes of "high memory" with this
selection. This is the usual setting.
And on a 2GB system would I get 1152 MB high and 896MB user?
Selecting "2GB" results in a "2GB/2GB" kernel/user split:
On a system with less than 1.75 gigabytes of physical memory,
this option will make it so no memory is mapped as "high".
Does that mean I get 128/1920 with 2GB of physical RAM?
And 0/1024 with 1GB of physical RAM?
And what are the cons of having no high memory?
To summarize, how much does all this affect performance and in what way?
--
Simon Oliver
prev parent reply other threads:[~2002-07-03 8:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 13:11 Kernel Compilation for Dual Xeon system Simon Oliver
2002-07-01 19:04 ` E. Robert Bogusta
2002-07-02 8:43 ` Simon Oliver
2002-07-02 17:46 ` E. Robert Bogusta
2002-07-03 8:12 ` Simon Oliver [this message]
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='afubs4$jdd$2@main.gmane.org' \
--to=simon.oliver@umist.ac.uk \
--cc=linux-smp@vger.kernel.org \
--cc=rob23@tmr.com \
--cc=suse-linux-e@suse.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