6,534
edits
Changes
+ secondary parameters
: The <code>barrier</code> is ignored, and the <code>limit</code> sets the limit.
The sum of <code>physpages.limit </code> and <code>swappages.limit </code> limits the maximum amount
of allocated memory which can be used by a container. When physpages limit
is reached, memory pages belonging to the container are pushed out to
swapping. Actual swap out occurs only if there is a global memory shortage
on the system.
=== Secondary parameters ===
In addition to <code>physpages</code> and <code>swappages</code> being set, it is ''currently'' recommended to:
* Set <code>kmemsize</code> to no more than 1/2 of <code>physpages</code>
* Set <code>dcachesize</code> to no more than 1/2 of <code>kmemsize</code>
* Set <code>lockedpages</code> to no more than 1/2 of <code>physpages</code>
VSwap CT config samples (like [http://git.openvz.org/?p=vzctl;a=blob;f=etc/conf/ve-vswap-256m.conf-sample ve-vswap-256m.conf-sample] that come with vzctl are currently implementing these recommendations.
{{Note|VSwap feature is still being worked on, so these recommendation might change in the future.}}
[[Category: UBC]]