6,534
edits
Changes
added some more...
Its configuration affects functionality and resource shortage reaction
of applications in the given Virtual Environment only.
== physpages ==
Total number of RAM pages used by processes in this Virtual Environment.
For memory pages used by several different Virtual Environments (mappings of
shared libraries, for example), only a fraction of a page is charged to each
Virtual Environment.
The sum of the <code>physpages</code> usage for all Virtual Environments
corresponds to the total number of pages used in the system by all
Virtual Environments.
<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 compatibility with future versions, the <code>barrier</code> of this
parameter should be set to <code>0</code> and the <code>limit</code> to
the maximal allowed value ([[MAX_ULONG]]).
== numfile ==
Number of open files.
The <code>barrier</code> should be set equal to the <code>limit</code>.
The configuration of this parameter doesn't affect security and
stability of the whole system or isolation between Virtual Environments.
Its configuration affects functionality and resource shortage reaction
of applications in the given Virtual Environment only.
== numflock ==
Number of file locks.
The configuration of this parameter should have a
gap between the <code>barrier</code> and the <code>limit</code>, as illustrated in
[[UBC configuration examples]].
Very high limits on <code>numflock</code> parameters and the big number
of file locks in the system may cause certain slowdown of
the whole system (but not fatal).
So, the limits on this parameter should be reasonable, depending
on the real requirements of the applications.
