From: Alexander Kapshuk <alexander.kapshuk@gmail.com>
To: gottlieb@nyu.edu, Alan McKinnon <alan.mckinnon@gmail.com>
Cc: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] re: NX (Execute Disable) protection cannot be enabled: non-PAE kernel! [dmesg]
Date: Wed, 09 Oct 2013 21:56:59 +0300 [thread overview]
Message-ID: <5255A6FB.3010404@gmail.com> (raw)
In-Reply-To: <87eh7vgpce.fsf@nyu.edu>
On 10/09/2013 05:17 AM, gottlieb@nyu.edu wrote:
> On Tue, Oct 08 2013, Alan McKinnon wrote:
>
>> That is correct, with 3G physica RAM, you will not benefit from using
>> PAE at all. I don't think it interferes with anything if you do have it,
>> I recall a time when RedHat shipped 32 bit kernels that were PAE-enabled.
>>
>> Briefly, the way it works is that the kernel assigns blocks of memory to
>> different processes. So a single process can still only access 4G of
>> memory, but two different process don't anymore have to address the same
>> 4G of memory like you must do without PAE. But you still don't get to
>> give your 32 bit database more than 4g of RAM
> Agreed. Virtual addresses refer to those in the program (really
> process). Physical addresses address refer to those in the hardware
> (i.e. addresses in the RAM itself). To have a single process able to
> access extra memory would be to increase the *virtual* address range.
> PAE (*physical* address extension) enables more RAM to be accessed (by
> the hardware not by a single process), but does not increase the virtual
> address range.
>
> When pdp-11s added I and D space, that increased the virtual address
> range by a factor of two. The I/D bit (instruction/data) was
> essentially an extra bit of virtual address.
>
> allan
>
Thanks a lot for the explanation. Much appreciated.
next prev parent reply other threads:[~2013-10-09 18:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 19:28 [gentoo-user] re: NX (Execute Disable) protection cannot be enabled: non-PAE kernel! [dmesg] Alexander Kapshuk
2013-10-07 19:42 ` Alan McKinnon
2013-10-08 17:04 ` Alexander Kapshuk
2013-10-08 21:20 ` Alan McKinnon
2013-10-09 2:17 ` gottlieb
2013-10-09 18:56 ` Alexander Kapshuk [this message]
2013-10-09 21:11 ` gottlieb
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=5255A6FB.3010404@gmail.com \
--to=alexander.kapshuk@gmail.com \
--cc=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=gottlieb@nyu.edu \
/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