summaryrefslogtreecommitdiff
path: root/man/systemd.resource-control.xml
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2014-05-24 18:02:16 -0400
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2014-05-24 18:50:21 -0400
commitb9acccb3c9795c88f1eca003480035917ff3c896 (patch)
tree6e75bfcc052d0bd85e1d9338ff68cf34851f21bb /man/systemd.resource-control.xml
parent68dd0956ef9d607e6ff9aea15883a2c290a33c2a (diff)
man: reword StartupCPUShares= description
Now that we have two options described in the same paragraph, we cannot use singular anymore.
Diffstat (limited to 'man/systemd.resource-control.xml')
-rw-r--r--man/systemd.resource-control.xml26
1 files changed, 14 insertions, 12 deletions
diff --git a/man/systemd.resource-control.xml b/man/systemd.resource-control.xml
index e0e49db7d..e91c260bf 100644
--- a/man/systemd.resource-control.xml
+++ b/man/systemd.resource-control.xml
@@ -119,22 +119,24 @@ along with systemd; If not, see <http://www.gnu.org/licenses/>.
<listitem>
<para>Assign the specified CPU time share weight to the
- processes executed. Takes an integer value. This controls
- the <literal>cpu.shares</literal> control group attribute,
- which defaults to 1024. For details about this control group
- attribute, see <ulink
+ processes executed. Those options take an integer value and
+ control the <literal>cpu.shares</literal> control group
+ attribute, which defaults to 1024. For details about this
+ control group attribute, see <ulink
url="https://www.kernel.org/doc/Documentation/scheduler/sched-design-CFS.txt">sched-design-CFS.txt</ulink>.
- The available CPU time is split up among all units within one
- slice relative to their CPU time share weight.</para>
+ The available CPU time is split up among all units within
+ one slice relative to their CPU time share weight.</para>
<para>While <varname>StartupCPUShares=</varname> only
applies to the startup phase of the system,
- <varname>CPUShares=</varname> 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.</para>
-
- <para>Implies <literal>CPUAccounting=true</literal>.</para>
+ <varname>CPUShares=</varname> applies to normal runtime of
+ the system, and if the former is not set also to the startup
+ phase. Using <varname>StartupCPUShares=</varname> allows
+ priorizing specific services at boot-up differently than
+ during normal runtime.</para>
+
+ <para>Those options imply
+ <literal>CPUAccounting=true</literal>.</para>
</listitem>
</varlistentry>