Changes

Jump to: navigation, search

UBC auxiliary parameters

28 bytes added, 05:45, 21 October 2011
m
Reverted edits by 109.228.171.118 (talk) to last revision by Kir
important for security and stability of the whole system. Auxiliary
parameters differ much from primary and secondary parameters in this respect.
 
== Introduction ==
The primary functions of auxiliary parameters are the following.
== physpages ==
Total number of RAM pages used by processes in this a container.
For memory pages used by several different containers (mappings of
containers.
For [[VSwap]]-enabled kernels, the <code>barrier</code> should be set to 0,and the <code>limit</code> limits the total size of RAM used by a container. For older kernels, <code>Physpagesphyspages</code> is an accounting-only parameter currently.In future OpenVZ releases, this parameter will allow to provide guaranteedamount of application memory, residing in RAM and not swappable.For compatibility with future versions, the The <code>barrier</code> of thisparameter should be set to <code>0</code> and the <code>limit</code> tothe maximal allowed value 'unlimited' ([[MAX_ULONGLONG_MAX]]).
== numfile ==
of total swap space in a container.
If the <code>limit</code> is set to [[MAX_ULONGLONG_MAX]] (which is the
in-kernel default for this parameter), all the swap space values
parameters (total, used, free) are reported as 0.
The value of <code>barrier</code> for this beancounter is ignored.
 
The value of <code>held</code> shows how much swap space
is currently being used for this container.

Navigation menu