X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.resource-control.xml;h=3c9fe6a9b148dc84f25b050e1a68e8721bbe8e32;hb=63c372cb9df3bee01e3bf8cd7f96f336bddda846;hp=e0e49db7d182a43f75cc07dea683f87dd6b2f8ec;hpb=9a0549093332880df47c4218209ce126b8586835;p=elogind.git
diff --git a/man/systemd.resource-control.xml b/man/systemd.resource-control.xml
index e0e49db7d..3c9fe6a9b 100644
--- a/man/systemd.resource-control.xml
+++ b/man/systemd.resource-control.xml
@@ -1,4 +1,4 @@
-
+
@@ -65,7 +65,7 @@ along with systemd; If not, see .
sockets, mount points, and swap devices share a subset of
configuration options for resource control of spawned
processes. Internally, this relies on the Control Groups
- kernel concept for organizing processes in a hierarchial tree of
+ kernel concept for organizing processes in a hierarchical tree of
named groups for the purpose of resource management.
This man page lists the configuration options shared by
@@ -119,22 +119,24 @@ along with systemd; If not, see .
Assign the specified CPU time share weight to the
- processes executed. Takes an integer value. This controls
- the cpu.shares control group attribute,
- which defaults to 1024. For details about this control group
- attribute, see cpu.shares control group
+ attribute, which defaults to 1024. For details about this
+ control group attribute, see sched-design-CFS.txt.
- The available CPU time is split up among all units within one
- slice relative to their CPU time share weight.
+ The available CPU time is split up among all units within
+ one slice relative to their CPU time share weight.
While StartupCPUShares= only
applies to the startup phase of the system,
- CPUShares= applies to the later runtime
- of the system, and if the former is not set also to the
- startup phase. This allows priorizing specific services at
- boot-up differently than during runtime.
-
- Implies CPUAccounting=true.
+ CPUShares= applies to normal runtime of
+ the system, and if the former is not set also to the startup
+ phase. Using StartupCPUShares= allows
+ prioritizing specific services at boot-up differently than
+ during normal runtime.
+
+ Those options imply
+ CPUAccounting=true.
@@ -146,14 +148,14 @@ along with systemd; If not, see .
executed. Takes a percentage value, suffixed with "%". The
percentage specifies how much CPU time the unit shall get at
maximum, relative to the total CPU time available on one
- CPU. Use values > 100% for alloting CPU time on more than
+ CPU. Use values > 100% for allotting CPU time on more than
one CPU. This controls the
cpu.cfs_quota_us control group
attribute. For details about this control group attribute,
see sched-design-CFS.txt.
- Example: CPUShares=20% ensures that
+ Example: CPUQuota=20% ensures that
the executed processes will never get more than 20% CPU time
on one CPU.
@@ -228,7 +230,7 @@ along with systemd; If not, see .
applies to the startup phase of the system,
BlockIOWeight= applies to the later runtime
of the system, and if the former is not set also to the
- startup phase. This allows priorizing specific services at
+ startup phase. This allows prioritizing specific services at
boot-up differently than during runtime.
Implies
@@ -392,6 +394,20 @@ along with systemd; If not, see .
+
+ Delegate=
+
+
+ Turns on delegation of further resource control
+ partitioning to processes of the unit. For unprivileged
+ services (i.e. those using the User=
+ setting) this allows processes to create a subhierarchy
+ beneath its control group path. For privileged services and
+ scopes this ensures the processes will have all control
+ group controllers enabled.
+
+
+