From d53d94743c5e5e3a4a668b0c707826a90a08949a Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Fri, 11 Sep 2015 16:48:24 +0200 Subject: core: refactor cpu shares/blockio weight cgroup logic Let's stop using the "unsigned long" type for weights/shares, and let's just use uint64_t for this, as that's what we expose on the bus. Unify parsers, and always validate the range for these fields. Correct the default blockio weight to 500, since that's what the kernel actually uses. When parsing the weight/shares settings from unit files accept the empty string as a way to reset the weight/shares value. When getting it via the bus, uniformly map (uint64_t) -1 to unset. Open up StartupCPUShares= and StartupBlockIOWeight= to transient units. --- man/systemd.resource-control.xml | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) (limited to 'man/systemd.resource-control.xml') diff --git a/man/systemd.resource-control.xml b/man/systemd.resource-control.xml index 6b9329bbee..98f4d75ddb 100644 --- a/man/systemd.resource-control.xml +++ b/man/systemd.resource-control.xml @@ -118,10 +118,11 @@ Assign the specified CPU time share weight to the - processes executed. Those options take an integer value and + processes executed. These 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. @@ -258,7 +259,7 @@ 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 + which defaults to 500. For details about this control group attribute, see blkio-controller.txt. The available IO bandwidth is split up among all units within -- cgit v1.2.3-54-g00ecf