Customizing Memory

After calling OEMInit, the kernel calls the function pointed to by pNKEnumExtensionDRAM if provided; otherwise, it calls OEMGetExtensionDRAM function to determine whether a contiguous bank of dynamic RAM (DRAM) is available on the target device. The kernel also calls this function when a user adds and removes memory. If a user adds memory, the kernel can continue processing without interruption. However, the kernel assumes that the additional memory, called extension memory, contains part of the object store, and therefore performs a cold boot to reinitialize the object store when a user removes the extension memory.

While you can define memory areas in the Config.bib file, you can define extension memory using OEMGetExtensionDRAM, OEMEnumExtensionDRAM, and the MainMemoryEndAddress global variable only. Because the kernel will use any memory that it is aware of, you should not define any memory areas that you want to reserve for a driver. For more information about the Config.bib file, see Config.bib Customization.

The following list shows the various ways you can customize how your system manages memory:

• Configuring System Memory
• Configuring Object Store Memory
• Creating Physical to Virtual Mappings
• Memory Addressing

See Also

How to Develop an OEM Adaptation Layer | Memory Architecture | Object Store and Registry

Last updated on Wednesday, April 13, 2005

© 2005 Microsoft Corporation. All rights reserved.