UBC auxiliary parameters - Revision history

Kir: Reverted edits by 109.228.171.118 (talk) to last revision by Kir

2011-10-21T05:45:11Z

Reverted edits by 109.228.171.118 (talk) to last revision by Kir

109.228.171.118: /* swappages */

2011-10-21T02:34:11Z

‎swappages

Kir: simplify toc

2011-10-01T21:01:03Z

simplify toc

Nathanhaigh: /* Units */

2011-08-15T23:13:19Z

‎Units

Nathanhaigh: Indented parameters by another heading level so toc is easier to follow. linked units subheading to the UBC parameter units page

2011-08-15T22:44:42Z

Indented parameters by another heading level so toc is easier to follow. linked units subheading to the UBC parameter units page

195.214.232.10: /* physpages */ +VSwap

2011-06-03T10:17:09Z

‎physpages: +VSwap

Kir: /* swappages */ MAX_ULONG -> LONG_MAX

2011-01-25T13:51:51Z

‎swappages: MAX_ULONG -> LONG_MAX

Kir: /* physpages */ MAX_ULONG -> LONG_MAX

2011-01-25T13:51:26Z

‎physpages: MAX_ULONG -> LONG_MAX

Kir: Reverted edits by 91.201.66.204 (Talk) to last revision by Kir

2010-11-13T08:34:03Z

Reverted edits by 91.201.66.204 (Talk) to last revision by Kir

91.201.66.204: Health

2010-11-13T08:28:03Z

Health

← Older revision		Revision as of 05:45, 21 October 2011
Line 186:		Line 186:
	to create more than 200–300 <code>numiptent</code>.		to create more than 200–300 <code>numiptent</code>.

−	~~I went~~ to ~~tons~~ of ~~links before~~ this, ~~what was I thiknnig?~~	+	== swappages ==
		+
		+	The amount of swap space to show in container.
		+
		+	{{Note\|this parameter is only available in RHEL5-based kernel since version 028stab060.2, in 2.6.27 since kiprensky.}}
		+
		+	The configuration of this parameter doesn't affect security and
		+	stability of the whole system or isolation between containers.
		+	Its configuration only affects the way OpenVZ kernel reports about
		+	available swap in a container. This is needed for some applications
		+	which refuse to run inside a container unless the kernel
		+	report that no less than some specific amount of swap is available.
		+
		+	If <code>limit</code> is set, its value is reported as the amount
		+	of total swap space in a container.
		+
		+	If the <code>limit</code> is set to [[LONG_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.

← Older revision		Revision as of 02:34, 21 October 2011
Line 186:		Line 186:
	to create more than 200–300 <code>numiptent</code>.		to create more than 200–300 <code>numiptent</code>.

−	~~== swappages ==~~	+	I went to tons of links before this, what was I thiknnig?
−
−	~~The amount of swap space to show in container.~~
−
−	~~{{Note\|this parameter is only available in RHEL5-based kernel since version 028stab060.2, in 2.6.27 since kiprensky.}}~~
−
−	~~The configuration of this parameter doesn't affect security and~~
−	~~stability of the whole system or isolation between containers.~~
−	~~Its configuration only affects the way OpenVZ kernel reports about~~
−	~~available swap in a container. This is needed for some applications~~
−	~~which refuse~~ to ~~run inside a container unless the kernel~~
−	~~report that no less than some specific amount of swap is available.~~
−
−	~~If <code>limit</code> is set, its value is reported as the amount~~
−	of ~~total swap space in a container.~~
−
−	~~If the <code>limit</code> is set to [[LONG_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.~~

@@ Line 52: / Line 52: @@
 administrators and hide them in “basic” management modes.
-== UBC Auxiliary Parameters ==
+== lockedpages ==
 Process pages not allowed to be swapped out (pages locked by <code>mlock(2)</code>).
@@ Line 72: / Line 68: @@
 of applications in the given container only.
-=== shmpages ===
+== shmpages ==
 The total size of shared memory (IPC, shared anonymous mappings and
 <code>tmpfs</code> objects).
@@ Line 84: / Line 80: @@
 of applications in the given container only.
-=== physpages ===
+== physpages ==
 Total number of RAM pages used by processes in a container.
@@ Line 101: / Line 97: @@
 <code>limit</code> to 'unlimited' ([[LONG_MAX]]).
-=== numfile ===
+== numfile ==
 Number of open files.
@@ Line 112: / Line 108: @@
 Note: actually currently adjusting the <code>barrier</code> will change the kernel behaviour on "pre-charging" the numfile resource. If you change one you will most likely not notice any changes in container behaviour at all. This ability was added for researching purposes purely.
-=== numflock ===
+== numflock ==
 Number of file locks.
@@ Line 125: / Line 121: @@
 on the real requirements of the applications.
-=== numpty ===
+== numpty ==
 Number of pseudo-terminals.
@@ Line 138: / Line 134: @@
 for one container is limited to <code>256</code>.
-=== numsiginfo ===
+== numsiginfo ==
 Number of <code>siginfo</code> structures.
@@ Line 153: / Line 149: @@
 the Linux default — <code>1024</code>.
-=== dcachesize ===
+== dcachesize ==
 The total size of <code>dentry</code> and <code>inode</code> structures locked in memory.
@@ Line 174: / Line 170: @@
 of applications in the given container only.
-=== numiptent ===
+== numiptent ==
 The number of NETFILTER (IP packet filtering) entries.
@@ Line 190: / Line 186: @@
 to create more than 200–300 <code>numiptent</code>.
-=== swappages ===
+== swappages ==
 The amount of swap space to show in container.
@@ Line 214: / Line 210: @@
 The value of <code>held</code> shows how much swap space
 is currently being used for this container.

← Older revision		Revision as of 23:13, 15 August 2011
Line 216:		Line 216:

	== Units ==		== Units ==
−	~~For full article, see: [[~~UBC parameter units]]	+	{{Main\|UBC parameter units}}

@@ Line 4: / Line 4: @@
 important for security and stability of the whole system. Auxiliary
 parameters differ much from primary and secondary parameters in this respect.
 The primary functions of auxiliary parameters are the following.
@@ Line 54: / Line 52: @@
 administrators and hide them in “basic” management modes.
-== lockedpages ==
+== UBC Auxiliary Parameters ==
 Process pages not allowed to be swapped out (pages locked by <code>mlock(2)</code>).
@@ Line 70: / Line 72: @@
 of applications in the given container only.
-== shmpages ==
+=== shmpages ===
 The total size of shared memory (IPC, shared anonymous mappings and
 <code>tmpfs</code> objects).
@@ Line 82: / Line 84: @@
 of applications in the given container only.
-== physpages ==
+=== physpages ===
 Total number of RAM pages used by processes in a container.
@@ Line 99: / Line 101: @@
 <code>limit</code> to 'unlimited' ([[LONG_MAX]]).
-== numfile ==
+=== numfile ===
 Number of open files.
@@ Line 110: / Line 112: @@
 Note: actually currently adjusting the <code>barrier</code> will change the kernel behaviour on "pre-charging" the numfile resource. If you change one you will most likely not notice any changes in container behaviour at all. This ability was added for researching purposes purely.
-== numflock ==
+=== numflock ===
 Number of file locks.
@@ Line 123: / Line 125: @@
 on the real requirements of the applications.
-== numpty ==
+=== numpty ===
 Number of pseudo-terminals.
@@ Line 136: / Line 138: @@
 for one container is limited to <code>256</code>.
-== numsiginfo ==
+=== numsiginfo ===
 Number of <code>siginfo</code> structures.
@@ Line 151: / Line 153: @@
 the Linux default — <code>1024</code>.
-== dcachesize ==
+=== dcachesize ===
 The total size of <code>dentry</code> and <code>inode</code> structures locked in memory.
@@ Line 172: / Line 174: @@
 of applications in the given container only.
-== numiptent ==
+=== numiptent ===
 The number of NETFILTER (IP packet filtering) entries.
@@ Line 188: / Line 190: @@
 to create more than 200–300 <code>numiptent</code>.
-== swappages ==
+=== swappages ===
 The amount of swap space to show in container.
@@ Line 212: / Line 214: @@
 The value of <code>held</code> shows how much swap space
 is currently being used for this container.

@@ Line 83: / Line 83: @@
 == physpages ==
-Total number of RAM pages used by processes in this container.
+Total number of RAM pages used by processes in a container.
 For memory pages used by several different containers (mappings of
@@ Line 92: / Line 92: @@
 containers.
-<code>Physpages</code> is an accounting-only parameter currently.
+For [[VSwap]]-enabled kernels, the <code>barrier</code> should be set to 0,
-In future OpenVZ releases, this parameter will allow to provide guaranteed
+and the <code>limit</code> limits the total size of RAM used by a container.
-amount of application memory, residing in RAM and not swappable.
-For compatibility with future versions, the <code>barrier</code> of this
+For older kernels, <code>physpages</code> is an accounting-only parameter.
-parameter should be set to <code>0</code> and the <code>limit</code> to
+The <code>barrier</code> should be set to <code>0</code> and the
-the maximal allowed value ([[LONG_MAX]]).
+<code>limit</code> to 'unlimited' ([[LONG_MAX]]).
 == numfile ==

@@ Line 204: / Line 204: @@
 of total swap space in a container.
-If the <code>limit</code> is set to [[MAX_ULONG]] (which is the
+If the <code>limit</code> is set to [[LONG_MAX]] (which is the
 in-kernel default for this parameter), all the swap space values
 parameters (total, used, free) are reported as 0.