From: William Lee Irwin III <wli@holomorphy.com>
To: Michael Vergoz <mvergoz@sysdoor.com>
Cc: alan@lxorguk.ukuu.org.uk, timothy.a.reed@lmco.com,
linux-kernel@vger.kernel.org
Subject: Re: High Mem Options
Date: Wed, 5 Mar 2003 05:10:56 -0800 [thread overview]
Message-ID: <20030305131056.GT1195@holomorphy.com> (raw)
In-Reply-To: <20030305140257.2ab08ab8.mvergoz@sysdoor.com>
On Wed, 5 Mar 2003 04:57:47 -0800, William Lee Irwin III wrote:
>> The cpu can't look at more than 4GB at a time.
>> Protected mode doesn't help this, turning paging on and PAE on does.
>> What it can do is point pagetables at different 4GB subsets of memory.
>> c.f. kmap_atomic() for how to window around using what's actually a
>> very small set of PTE's.
On Wed, Mar 05, 2003 at 02:02:57PM +0100, Michael Vergoz wrote:
> Right, but if the pagetable pointing to a different 4GB subsets of
> memory. The performance of the system can be disastrous, not?
Well, the TLB gets blown away at the drop of a hat. Things just have
lower scaling factors with respect to memory than say, 64-bit, though
Linux doesn't do anything about TLB coverage on 64-bit yet anyway.
It might be better to take this one to kernelnewbies@nl.linux.org
-- wli
next prev parent reply other threads:[~2003-03-05 13:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 11:28 High Mem Options Reed, Timothy A
2003-03-05 12:11 ` Michael Vergoz
2003-03-05 13:36 ` Alan Cox
2003-03-05 12:49 ` Michael Vergoz
2003-03-05 12:57 ` William Lee Irwin III
2003-03-05 13:02 ` Michael Vergoz
2003-03-05 13:10 ` William Lee Irwin III [this message]
2003-03-09 2:41 ` Bill Davidsen
2003-03-05 14:21 ` Alan Cox
2003-03-05 12:26 ` William Lee Irwin III
2003-03-05 20:31 ` Gerrit Huizenga
2003-03-05 20:58 ` William Lee Irwin III
2003-03-05 21:11 ` Gerrit Huizenga
2003-03-05 21:34 ` Martin J. Bligh
2003-03-05 13:38 ` Alan Cox
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=20030305131056.GT1195@holomorphy.com \
--to=wli@holomorphy.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mvergoz@sysdoor.com \
--cc=timothy.a.reed@lmco.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