summaryrefslogtreecommitdiff
path: root/man/systemd.resource-control.xml
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2023-03-07 16:08:16 +0100
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2023-03-07 16:22:13 +0100
commitdca031d2290311d8670d34fd758397644796e114 (patch)
treee80f8d5f34e18540b6df5992f9374906c2a8d258 /man/systemd.resource-control.xml
parent396d298d6b0c50a3ab3242392de43dd50df6d45f (diff)
downloadsystemd-dca031d2290311d8670d34fd758397644796e114.tar.gz
man: add a note about session autogrouping
When cpu controller is disabled, thing would often still behave as if it was. And since the cpu controller can be enabled "magically" e.g. by starting user@1000, add a note for users to be careful. Autogrouping is described well in the man page, incl. how to enable or disable it, so it should be enough to refer to that.
Diffstat (limited to 'man/systemd.resource-control.xml')
-rw-r--r--man/systemd.resource-control.xml7
1 files changed, 7 insertions, 0 deletions
diff --git a/man/systemd.resource-control.xml b/man/systemd.resource-control.xml
index 1cfe1ed52a..45b006be57 100644
--- a/man/systemd.resource-control.xml
+++ b/man/systemd.resource-control.xml
@@ -225,6 +225,13 @@ CPUWeight=20 DisableControllers=cpu / \
<varname>CPUWeight=</varname> applies to normal runtime of the system, and if the former is not set also to
the startup and shutdown phases. Using <varname>StartupCPUWeight=</varname> allows prioritizing specific services at
boot-up and shutdown differently than during normal runtime.</para>
+
+ <para>In addition to the resource allocation performed by the <option>cpu</option> controller, the
+ kernel may automatically divide resources based on session-id grouping, see "The autogroup feature"
+ in <citerefentry
+ project='man-pages'><refentrytitle>sched</refentrytitle><manvolnum>7</manvolnum></citerefentry>.
+ The effect of this feature is similar to the <option>cpu</option> controller with no explicit
+ configuration, so users should be careful to not mistake one for the other.</para>
</listitem>
</varlistentry>