Editing UBC auxiliary parameters
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 81: | Line 81: | ||
== physpages == | == physpages == | ||
− | Total number of RAM pages used by processes in | + | Total number of RAM pages used by processes in this container. |
For memory pages used by several different containers (mappings of | For memory pages used by several different containers (mappings of | ||
Line 90: | Line 90: | ||
containers. | containers. | ||
− | + | <code>Physpages</code> is an accounting-only parameter currently. | |
− | + | In future OpenVZ releases, this parameter will allow to provide guaranteed | |
− | + | amount of application memory, residing in RAM and not swappable. | |
− | For | + | For compatibility with future versions, the <code>barrier</code> of this |
− | + | parameter should be set to <code>0</code> and the <code>limit</code> to | |
− | <code>limit</code> to | + | the maximal allowed value ([[LONG_MAX]]). |
== numfile == | == numfile == |