Title: | VAX and Alpha VMS |
Notice: | This is a new VMSnotes, please read note 2.1 |
Moderator: | VAXAXP::BERNARDO |
Created: | Wed Jan 22 1997 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 703 |
Total number of notes: | 3722 |
In the description of the $LCKPAG system service it says: SS$_LCKPAGFUL The system-defined maximum limit on the number of pages that can be locked in memory has been reached. Is it possible to reduce the maximum via one or more SYSGEN parameters? I searched through the output of SHOW /ALL on my system (Alpha running V6.2-1H3) but didn't find any parameter related to the maximum number of locked pages. I'd like to reduce the maximum number of lockable pages, if possible, to prevent a memory test program from locking more than 90% of physical memory. Any suggestions would be appreciated. Greg
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
396.1 | depends... | EVMS::KUEHNEL | Andy K�hnel | Thu Mar 27 1997 09:23 | 12 |
Up to V7.1, all we check for locking pages is decrementing a counter from its initial hard-coded very high value (%x40000000). We would return with SS$_LCKPAGFUL if this counter gets to 0 - a highly unlikely case. You can of course write a little kernel mode routine to simply decrease this counter to a more reasonable value. For the RAVEN release on Alpha this mechanism has been changed. You can no longer lock pages in memory if this would reduce the fluid page count below the minimum required to keep VMS alive. This minimum is currently defined as the sum of MPW_LOLIMIT + FREELIM + maximum size of swap image | |||||
396.2 | Thank you | GREGOR::OPP | Thu Mar 27 1997 12:44 | 6 | |
Thank you for the explanation. I'll stick to my current imple- mentation of limiting the number of memory test processes via a command procedure that gets the free space from "SHOW MEMORY". Greg |