Mailinglist Archive: opensuse (3605 mails)
| < Previous | Next > |
Re: [SLE] 32-bit machines hit physical RAM limit at 4GB?
- From: Per Jessen <per@xxxxxxxxxxxx>
- Date: Mon, 12 Jun 2006 16:15:38 +0200
- Message-id: <e6jsua$b9h$2@xxxxxxxxxxxxxxxx>
Bryan J. Smith wrote:
> On Mon, 2006-06-12 at 15:03 +0200, Per Jessen wrote:
>> Isn't that more or less what I started this thread with?
>
> The problem is that you're applying kernel modes to application ABI.
I am? I'll take your word for it.
>> Which is what I am ALSO saying. The application does not go beyond
>> the 4Gb address space, the operating system (in our case Linux) does
>> that for the application.
>
> Again, re-read this portion ...
>
> "Because processes running in these environments have 32-bit
> pointers"
>
> First, the processes are built for 32-bit/4GiB pointers. That's a
> _hard_ limit.
Bryan, sometimes you do need to read what others say - you're preaching
to the choir. I started out saying that the 4Gb address space for the
application does NOT change just because we make the OS PAE-aware.
> That does _not_ mean the applications can use 36-bit. That means the
> OS is using page translation to "window" 36-bit physical memory into
> 32-bit flat memory.
I know, and I've never said otherwise. James Knott was the one claiming
that the application had to be PAE-aware in order to make use (e.g.
execute in) of physical memory above 4Gb.
/Per Jessen, Zürich
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx
> On Mon, 2006-06-12 at 15:03 +0200, Per Jessen wrote:
>> Isn't that more or less what I started this thread with?
>
> The problem is that you're applying kernel modes to application ABI.
I am? I'll take your word for it.
>> Which is what I am ALSO saying. The application does not go beyond
>> the 4Gb address space, the operating system (in our case Linux) does
>> that for the application.
>
> Again, re-read this portion ...
>
> "Because processes running in these environments have 32-bit
> pointers"
>
> First, the processes are built for 32-bit/4GiB pointers. That's a
> _hard_ limit.
Bryan, sometimes you do need to read what others say - you're preaching
to the choir. I started out saying that the 4Gb address space for the
application does NOT change just because we make the OS PAE-aware.
> That does _not_ mean the applications can use 36-bit. That means the
> OS is using page translation to "window" 36-bit physical memory into
> 32-bit flat memory.
I know, and I've never said otherwise. James Knott was the one claiming
that the application had to be PAE-aware in order to make use (e.g.
execute in) of physical memory above 4Gb.
/Per Jessen, Zürich
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx
| < Previous | Next > |