On Sun, 2006-06-11 at 12:40 -0400, James Knott wrote:
While I don't have the exact details of PAE, in general memory mapping works by mapping physical memory outside of the normal addressing range, to an address within that range. This means that only a portion of that physical address range can be visible at a given time. An application has to be able to tell the operating system what portion of the physical memory it wants and also where in address space it wants it to be located.
There is a whole can of worms you open when you start talking about 32-bit flat, PAE 36-bit (PPro+/Athlon+) and newer PAE 52-bit (x86-64) from translation and performance standpoints.
Here's some more info. http://www.microsoft.com/whdc/system/platform/server/PAE/pae_os.mspx
Know that Linux's PAE and non-PAE memory models and approaches differ _radically_ from NT's. -- 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