{| class="wikitable"{UBC toc}} All the existing parameters are listed in the [[UBC parameters table]].! Name !! DescriptionBy importance, the parameters are divided into 3 groups: [[UBC primary parameters|-primary parameters]],[[UBC secondary parameters|secondary parameters]] and [[UBC auxiliary parameters| colspanauxiliary parameters]].More detailed description of the parameters and the resource controlmechanisms governed by the parameters is provided in the appropriate articles. ="2" align="center" | Primary General information about all parameters==|-All resource control parameters have some common properties| numproc || Number of processes and threadssome differences.|-| numtcpsock || Number <ol><li>Most parameters provide both accounting of TCP socketssome system resourceand allow controlling its consumption.|-The exceptions are <code>physpages</code> (accounting only)| numothersock || Number of sockets other than TCPand <code>vmguarpages</code> (no accounting, control only), explained below.</li>|-| vmguarpages || Memory allocation guarantee<li>Each parameter has 2 configuration variables, in pagescalled <code>barrier</code> and <code>limit</code>.|-| colspan="Although both 2" align="center" | Secondary variables are changeable, only one or none of them may beeffectively used for the resource control for some parameters.|For example, <code>physpages</code> is an accounting-only parameter and both its| kmemsize || Size of unswappable kernel memory, allocated for processes configuration variables are not effectively used in this [[VE]]the current OpenVZversion.|-| tcpsndbuf || Total size The description of each parameter explains the meaning of TCP send buffersthe <code>barrier</code>and the <code>limit</code> and what they should be set to if they are noteffectively used.|-| tcprcvbuf || Total size of TCP receive buffersIn general, for all parameters the <code>barrier</code> should not be greater thanthe <code>limit</code>.</li> |-<li>The parameters control| othersockbuf || Total size how the resources are distributed between containers in terms of UNIX-domain socket buffers* limits, i.e.&nbsp;upper boundaries on what this container can consume, UDP and other datagram protocol send buffers* guarantees, i.e.|-| dgramrcvbuf || Receive buffers &nbsp;mechanisms ensuring that this container can get the assigned “resources” regardless of UDP the activity and the amount of resources required by other datagram protocolscontainers.|-| The parameters containing “<code>guar</code>” in their names,i.e.&nbsp;<code>vmguarpages</code> and <code>oomguarpages || The guaranteed amount </code> are container'sguarantees.They guarantee availability of memory for resources and certain service levelup to the case value, specified by the memory is “over-booked” (out-of-memory kill <code>barrier</code>,and do not guarantee)above the <code>barrier</code>.However, these parameters do not impose usage restrictions.The guarantees are discussed in more detail in pagesthe paragraphs describingthese parameters.|-| privvmpages || Memory allocation The <code>limit</code> of <code>vmguarpages</code> and <code>oomguarpages</code> should beset to the maximal value [[LONG_MAX]].</li> <li>For some resource limiting parameters, such as <code>kmemsize</code>, in pagesboth <code>barrier</code> and <code>limit</code> settings are effectively used.|-If the resource usage exceeds the <code>barrier</code> but doesn't exceed the| colspan="2" align="center" | Auxiliary parameters<code>limit</code>, vital operations (such as process stack expansion)|-are still allowed to allocate new| lockedpages || Process pages resources, and other ones are not allowed to be swapped out (pages locked by .A gap between the <code>barrier</code> and the <code>mlock(2)limit</code>)gives applicationsbetter chances to handle resource shortage gracefully.|-| shmpages || Total size of shared memory (IPCFor other resource limiting parameters, such as <code>numproc</code>, shared anonymous mappings <code>barrier</code> and <code>tmpfslimit</code> objects), in pagesshould be set to the same value.|-</li>| physpages || Total number of RAM pages used by processes.|-<li>| numfile || Number Each parameter has “natural units of open files.measurement” — the units|-| numflock || Number of file locksmeasurement of values shown via <code>/proc/user_beancounters</code> interface and accepted by [[vzctl]].|-Values related to parameters with names starting with <code>num</code> are measured| numpty || Number of pseudo-terminalsin pieces.|-| numsiginfo || Number of Values related to parameters with names ending with <code>siginfopages</code> structures.are measured|in memory pages (memory page is equal to 4 kilobytes on IA-32 hardware).| dcachesize || Total size of The remaining values (parameters ending with <code>dentrysize</code> and <code>inodebuf</code> structures locked )are measured in memorybytes. See more at [[UBC parameter units]].|-</li> </ol> | numiptent || Number The properties of NETFILTER (IP packet filtering) entriesparameters are summarized in [[UBC parameter properties]]. {{Note|Continue reading with [[UBC primary parameters]], [[UBC secondary parameters]] and [[UBC auxiliary parameters]].}}