James Knott wrote:
The application is not supposed to know. Really. Maybe some of its virtual memory is mapped to physical memory at >4Gb, but the application should not and does not care.
I think we've reached the point where you're trying to strech a point.
Perhaps - though I believe I've been arguing the same thing all along.
My entire discussion has been about software in general, trying to access memory beyond the natural 4 GB limit of a 32 bit CPU. Whether it's the OS or app is irrelevant to the discussion.
No, I think that's exactly why we haven't agreed. You've been talking about applications, and I've been saying that the application need not know and that whether the OS is PAE-aware or not does not affect it. (except in performance).
While the OS may be using it, an app still cannot access anything beyond that limit.
Isn't that more or less what I've been saying all along? That the applications virtual address space does not change just because the kernel is PAE-aware? The application will always be using virtual addresses in the 0-4Gb range, even if these may quite well be mapped to physical memory above 16G. /Per Jessen, Zürich -- 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