From: Roland Dreier <rdreier@cisco.com>
To: joe Shmoe <jsmoe3@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel page table mapping for >1GB <3 GB for x86 arch without PAE
Date: Fri, 28 Aug 2009 11:12:26 -0700 [thread overview]
Message-ID: <ada8wh3renp.fsf@cisco.com> (raw)
In-Reply-To: <374672.36063.qm@web45210.mail.sp1.yahoo.com> (joe Shmoe's message of "Fri, 28 Aug 2009 11:08:08 -0700 (PDT)")
> Assuming I have 3GB RAM, why does not kernel create page tables in a way that all of this 3GB physical memory can be addressed . (for x86 arch 32 bit with PAE disabled )
>
> I understand the 3GB/1GB split for user/kernel address space.Isn't this just a matter of setting up the page table entries in such a way that so all the available RAM upto 3GB can mapped in the kernel page tables. In this way CPU's MMU can take care of mapping any virtual address within first 4GB to physical address using the page table entries regardless of a process is in kernel/user mode.
On a 32-bit architecture, there is only 4GB of address space available.
If the kernel uses 3GB of address space for a direct mapping of physical
memory, then only 1GB is available for everything else (userspace,
vmalloc, etc). BTW, this is available by enabling CONFIG_VMSPLIT_1G.
- R.
next prev parent reply other threads:[~2009-08-28 18:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 18:08 kernel page table mapping for >1GB <3 GB for x86 arch without PAE joe Shmoe
2009-08-28 18:12 ` Roland Dreier [this message]
2009-08-28 18:40 ` joe Shmoe
2009-08-28 19:13 ` Valdis.Kletnieks
2009-08-28 19:44 ` joe Shmoe
2009-08-28 19:53 ` Alan Cox
2009-08-28 20:23 ` joe Shmoe
2009-08-28 22:16 ` Alan Cox
2009-08-29 0:20 ` joe Shmoe
2009-08-29 13:05 ` Alan Cox
2009-08-29 14:40 ` joe Shmoe
2009-08-28 21:07 ` joe Shmoe
2009-08-28 22:11 ` Alan Cox
2009-08-28 19:49 ` Roland Dreier
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=ada8wh3renp.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=jsmoe3@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
/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