X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd.resource-control.xml;h=b050a1752348524d7f8a3924d1452bf28e5791d3;hp=33d2f2e10263a0596156528b70915437ef83e2de;hb=85a8eeee36b57c1ab382b0225fa9a87525bbeee9;hpb=95ae05c0e79868c22b3e8e6fbc53432786876730
diff --git a/man/systemd.resource-control.xml b/man/systemd.resource-control.xml
index 33d2f2e10..b050a1752 100644
--- a/man/systemd.resource-control.xml
+++ b/man/systemd.resource-control.xml
@@ -1,4 +1,4 @@
-
+
@@ -115,18 +115,28 @@ along with systemd; If not, see .
CPUShares=weight
+ StartupCPUShares=weight
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 sched-design-CFS.txt
- The available CPU time is split up among all units within a
- slice relative to their CPU time share weight.
-
- Implies CPUAccounting=true.
+ processes executed. Those options take an integer value and
+ control the 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.
+
+ While StartupCPUShares= only
+ applies to the startup phase of the system,
+ CPUShares= applies to normal runtime of
+ the system, and if the former is not set also to the startup
+ phase. Using StartupCPUShares= allows
+ priorizing specific services at boot-up differently than
+ during normal runtime.
+
+ Those options imply
+ CPUAccounting=true.
@@ -135,20 +145,17 @@ along with systemd; If not, see .
Assign the specified CPU time quota to the processes
- executed. Takes a percentage value (suffixed with "%") or an
- absolute time (suffixed by one of the common time units, us,
- ms, s, ...). 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 one CPU. If an absolute time is specified
- the processes of this unit will get this much absolute time
- within each quota period, at maximum. This controls the
+ 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
+ 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.
@@ -156,32 +163,6 @@ along with systemd; If not, see .
-
- CPUQuotaPeriodSec=
-
-
- Specify the CPU quota period to use. Defaults to
- 100ms. This controls the cpu.cfs_period_us
- control group attribute. For details about this control
- group attribute, see sched-design-CFS.txt.
-
- Implies CPUAccounting=true.
-
-
-
-
- StartupCPUShares=weight
-
-
- Similar to CPUShares=. However,
- only be assigned on startup state. After finishing startup, will be
- re-assigned by CPUShares=. If
- CPUShares= is not specified, then it will be
- assigned to default(1024).
-
-
-
MemoryAccounting=
@@ -233,37 +214,30 @@ along with systemd; If not, see .
BlockIOWeight=weight
+ StartupBlockIOWeight=weight
- Set the default
- overall block IO weight for the
- executed processes. Takes a single
- weight value (between 10 and 1000) to
- set the default block IO weight. This
- controls the
- blkio.weight
- control group attribute, which
- defaults to 1000. For details about
- this control group attribute, see
- blkio-controller.txt.
+ Set the default overall block IO weight for
+ the executed processes. Takes a single weight value (between
+ 10 and 1000) to set the default block IO weight. This controls
+ the blkio.weight control group attribute,
+ which defaults to 1000. For details about this control group
+ attribute, see blkio-controller.txt.
+ The available IO bandwidth is split up among all units within
+ one slice relative to their block IO weight.
+
+ While StartupBlockIOWeight= only
+ 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
+ boot-up differently than during runtime.
Implies
BlockIOAccounting=true.
-
- StartupBlockIOWeight=weight
-
-
- Similar to BlockIOWeight=. However,
- only be assigned on startup state. After finishing startup, will be
- re-assigned by BlockIOWeight=. If
- BlockIOWeight= is not specified, then it will be
- assigned to default(1000).
-
-
-
BlockIODeviceWeight=device weight
@@ -420,6 +394,20 @@ along with systemd; If not, see .
+
+ Delegate=
+
+
+ Turns on delegation of further resource control
+ partitioning to processes of the unit. For unpriviliged
+ services (i.e. those using the User=
+ setting) this allows processes to create a subhierarchy
+ beneath its control group path. For priviliged services and
+ scopes this ensures the processes will have all control
+ group controllers enabled.
+
+
+