On Mon, 2006-06-12 at 14:35 +0200, Per Jessen wrote:
But we are talking about an application accessing memory, which on Linux is done exclusively through the virtual memory manager. That the VMM will use the PAE for addressing up to 64Gb of physical memory does not concern the application.
Also, to come at it from the VMM avenue ... 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. It also can't address issues where an application is built for the 1-3GiB model in its object code. That's utterly different than the kernel using page translation and relocating _individual_ programs. 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. -- Bryan J. Smith Professional, technical annoyance mailto:b.j.smith@ieee.org http://thebs413.blogspot.com ------------------------------------------------------- Illegal Immigration = "Representation Without Taxation" -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com