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:10:22 +0200
- Message-id: <e6jske$b9h$1@xxxxxxxxxxxxxxxx>
Bryan J. Smith wrote:
> While the VMM _can_ address the issue of _all_ programs using more
> than 1-3GiB or even 4GiB _total_ for _all_ applications, it can_not_
> address the program's issue of allocating more memory than allowed by
> 32-bit/4GiB pointers.
This is exactly what I've been saying right from the start.
> We're not talking programs that have to "work with" the kernel at
> "it's level" to allocate total memory in excess of what can be done
> for typical process user-space -- let alone _hard_ 32-bit/4GiB pointer
> limitations.
I didn't think we were, no.
/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
> While the VMM _can_ address the issue of _all_ programs using more
> than 1-3GiB or even 4GiB _total_ for _all_ applications, it can_not_
> address the program's issue of allocating more memory than allowed by
> 32-bit/4GiB pointers.
This is exactly what I've been saying right from the start.
> We're not talking programs that have to "work with" the kernel at
> "it's level" to allocate total memory in excess of what can be done
> for typical process user-space -- let alone _hard_ 32-bit/4GiB pointer
> limitations.
I didn't think we were, no.
/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 > |