|
Home > Archive > Unix True 64 > September 2006 > VM maxentries and vpagemax in 5.1B
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
VM maxentries and vpagemax in 5.1B
|
|
| Stephen Jones 2006-09-02, 7:38 am |
| Hi, I'm using a software system that requires these two vm kernel parameters
to be tuned: maxentries (1024) and vpagemax (65536).
Unfortunately these kernel parameters seem to have been depreciated.
After doing some researching, I assumed that enabling 'vm_bigpg_enable' which
seems to meet the requirement for vpagemax would do what I needed to do.
When I start up the application, the error I get is:
Unable to allocate trace buffer
Out of Memory
| |
| mooremar@gmail.com 2006-09-06, 7:49 pm |
|
Stephen Jones wrote:
> Hi, I'm using a software system that requires these two vm kernel parameters
> to be tuned: maxentries (1024) and vpagemax (65536).
>
> Unfortunately these kernel parameters seem to have been depreciated.
>
> After doing some researching, I assumed that enabling 'vm_bigpg_enable' which
> seems to meet the requirement for vpagemax would do what I needed to do.
>
> When I start up the application, the error I get is:
>
> Unable to allocate trace buffer
> Out of Memory
The virtual memory subsystem underwent significant changes from V4 ot
V5, and these two parameters don't exist (nor is there any equivalent).
Just ignore them and don't worry about it.
I would also suggest returning to the unenabled state for big pages,
unless your application specifically requires them to be enabled.
Martin
|
|
|
|
|