HOWTO: Change Max Memory Allowed with MmProbeAndLockPages

Last reviewed: February 17, 1998
Article ID: Q121965
The information in this article applies to:

- Microsoft Win32 Device Development Kit (DDK) for Windows NT,

  versions 3.1, 3.5, 3.51

SUMMARY

When using MmProbeAndLockPages, you need to remember that there is a limit to the amount of memory that can be locked down by MmProbeAndLockPages. The amount of memory is normally determined by the computer system at boot time. However, if you need to probe and lock more memory than is being allowed, there is a registry parameter that you can configure to allow you to determine the amount of memory available to probe and lock.

A key named IoPageLockLimit is located in HKEY_LOCAL_MACHINE\CurrentControlSet\Control\Session Manager\Memory Management. By default, this limit is 0, which indicates to the system that it should use a built-in algorithm to determine the amount of memory. You can change this value to indicate the number of bytes that can be used for MmProbeAndLockPages.

NOTE: Be careful when changing this value. The default value computed by the system when IoPageLockLimit is 0 is tuned specifically for system performance. Allowing the system to lock down more memory can have a detrimental effect on system performance.


Additional query words: NT DDK kernel mode memory
Version : WINNT:3.1,3.5,3.51;
Platform : winnt
Issue type : kbhowto


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 17, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.