From: Robert Read <rread@datarithm.net>
To: michaelc <michaelc@turbolinux.com.cn>
Cc: linux-kernel@vger.kernel.org
Subject: Re: can somebody explain how linux support 64G memory
Date: Tue, 20 Feb 2001 21:45:22 -0800 [thread overview]
Message-ID: <20010220214522.A5925@tenchi.datarithm.net> (raw)
In-Reply-To: <544126968.20010221104430@turbolinux.com.cn>
In-Reply-To: <544126968.20010221104430@turbolinux.com.cn>; from michaelc@turbolinux.com.cn on Wed, Feb 21, 2001 at 10:44:30AM +0800
There are two ways, the PAE flag and the PSE-36 feature introduced in
P3. These extensions are documented in the IA-32 Intel Architecture
Software Developer's Manuals, which you can find here:
http://developer.intel.com/design/Pentium4/manuals/
Look in Volume 3, Chapter 3 for this info.
robert
On Wed, Feb 21, 2001 at 10:44:30AM +0800, michaelc wrote:
> Hi,
> How does linux support more than 4G memory? I 've read the
> documentation of Intel IA-32 Architecture, I knew that OS
> just address up to 4G physical address space, If OS want to
> access additional 4-GByte section of physical memory, it must
> change the pointer in register CR3 or entries in the
> page-directory-pointer table. That means that Linux just has
> up to 4-GByte page mapping at one time , is that right?
>
>
>
> --
> Best regards,
> michael chen mailto:michaelc@turbolinux.com.cn
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-02-21 5:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 2:44 michaelc
2001-02-21 5:45 ` Robert Read [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=20010220214522.A5925@tenchi.datarithm.net \
--to=rread@datarithm.net \
--cc=linux-kernel@vger.kernel.org \
--cc=michaelc@turbolinux.com.cn \
/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®