From 78e9bb837c258ac0ec7712b3d612cc2f407e731e Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Wed, 12 Jun 2024 05:50:42 +0200 Subject: Merging upstream version 256. Signed-off-by: Daniel Baumann --- man/systemd.resource-control.xml | 80 ++++++++++++++++++++++++++-------------- 1 file changed, 53 insertions(+), 27 deletions(-) (limited to 'man/systemd.resource-control.xml') diff --git a/man/systemd.resource-control.xml b/man/systemd.resource-control.xml index 5c61b74..3773a38 100644 --- a/man/systemd.resource-control.xml +++ b/man/systemd.resource-control.xml @@ -1,6 +1,6 @@ + "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> @@ -151,10 +151,13 @@ CPUWeight=20 DisableControllers=cpu / \ applies to all user slices. - See the New - Control Group Interfaces for an introduction on how to make - use of resource control APIs from programs. + + + <para>See the <ulink + url="https://systemd.io/CONTROL_GROUP_INTERFACE">New + Control Group Interfaces</ulink> for an introduction on how to make + use of resource control APIs from programs.</para> + </refsect2> </refsect1> <refsect1> @@ -406,7 +409,9 @@ CPUWeight=20 DisableControllers=cpu / \ system. If assigned the special value <literal>infinity</literal>, no memory throttling is applied. This controls the <literal>memory.high</literal> control group attribute. For details about this control group attribute, see - <ulink url="https://docs.kernel.org/admin-guide/cgroup-v2.html#memory-interface-files">Memory Interface Files</ulink>.</para> + <ulink url="https://docs.kernel.org/admin-guide/cgroup-v2.html#memory-interface-files">Memory Interface Files</ulink>. + The effective configuration is reported as <varname>EffectiveMemoryHigh=</varname> + (see also <varname>EffectiveMemoryMax=</varname>).</para> <para>While <varname>StartupMemoryHigh=</varname> applies to the startup and shutdown phases of the system, <varname>MemoryHigh=</varname> applies to normal runtime of the system, and if the former is not set also to @@ -434,7 +439,9 @@ CPUWeight=20 DisableControllers=cpu / \ percentage value may be specified, which is taken relative to the installed physical memory on the system. If assigned the special value <literal>infinity</literal>, no memory limit is applied. This controls the <literal>memory.max</literal> control group attribute. For details about this control group attribute, see - <ulink url="https://docs.kernel.org/admin-guide/cgroup-v2.html#memory-interface-files">Memory Interface Files</ulink>.</para> + <ulink url="https://docs.kernel.org/admin-guide/cgroup-v2.html#memory-interface-files">Memory Interface Files</ulink>. + The effective configuration is reported as <varname>EffectiveMemoryMax=</varname> (the value is + the most stringent limit of the unit and parent slices and it is capped by physical memory).</para> <para>While <varname>StartupMemoryMax=</varname> applies to the startup and shutdown phases of the system, <varname>MemoryMax=</varname> applies to normal runtime of the system, and if the former is not set also to @@ -480,7 +487,7 @@ CPUWeight=20 DisableControllers=cpu / \ cache for swap pages. It takes pages that are in the process of being swapped out and attempts to compress them into a dynamically allocated RAM-based memory pool. If the limit specified is hit, no entries from this unit will be stored in the pool until existing entries are faulted back or written out to disk. See the kernel's - <ulink url="https://www.kernel.org/doc/html/latest/admin-guide/mm/zswap.html">Zswap</ulink> documentation for more details.</para> + <ulink url="https://docs.kernel.org/admin-guide/mm/zswap.html">Zswap</ulink> documentation for more details.</para> <para>Takes a size in bytes. If the value is suffixed with K, M, G or T, the specified size is parsed as Kilobytes, Megabytes, Gigabytes, or Terabytes (with the base 1024), respectively. If assigned the @@ -497,6 +504,23 @@ CPUWeight=20 DisableControllers=cpu / \ </listitem> </varlistentry> + <varlistentry> + <term><varname>MemoryZSwapWriteback=</varname></term> + + <listitem> + <para>This setting controls the <option>memory</option> controller in the unified hierarchy.</para> + + <para>Takes a boolean argument. When true, pages stored in the Zswap cache are permitted to be + written to the backing storage, false otherwise. Defaults to true. This allows disabling + writeback of swap pages for IO-intensive applications, while retaining the ability to store + compressed pages in Zswap. See the kernel's + <ulink url="https://docs.kernel.org/admin-guide/mm/zswap.html">Zswap</ulink> documentation + for more details.</para> + + <xi:include href="version-info.xml" xpointer="v256"/> + </listitem> + </varlistentry> + <varlistentry> <term><varname>AllowedMemoryNodes=</varname></term> <term><varname>StartupAllowedMemoryNodes=</varname></term> @@ -559,8 +583,9 @@ CPUWeight=20 DisableControllers=cpu / \ number of tasks on the system. If assigned the special value <literal>infinity</literal>, no tasks limit is applied. This controls the <literal>pids.max</literal> control group attribute. For details about this control group attribute, the - <ulink url="https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html#pid">pids controller - </ulink>.</para> + <ulink url="https://docs.kernel.org/admin-guide/cgroup-v2.html#pid">pids controller + </ulink>. + The effective configuration is reported as <varname>EffectiveTasksMax=</varname>.</para> <para>The system default for this setting may be controlled with <varname>DefaultTasksMax=</varname> in @@ -1100,6 +1125,7 @@ NFTSet=cgroup:inet:filter:my_service user:inet:filter:serviceuser } }</programlisting> </para> + <xi:include href="system-only.xml" xpointer="singular"/> <xi:include href="version-info.xml" xpointer="v255"/></listitem> </varlistentry> @@ -1666,22 +1692,22 @@ DeviceAllow=/dev/loop-control <refsect1> <title>See Also - - systemd1, - systemd-system.conf5, - systemd.unit5, - systemd.service5, - systemd.slice5, - systemd.scope5, - systemd.socket5, - systemd.mount5, - systemd.swap5, - systemd.exec5, - systemd.directives7, - systemd.special7, - systemd-oomd.service8, - The documentation for control groups and specific controllers in the Linux kernel: - Control Groups v2. - + + systemd1 + systemd-system.conf5 + systemd.unit5 + systemd.service5 + systemd.slice5 + systemd.scope5 + systemd.socket5 + systemd.mount5 + systemd.swap5 + systemd.exec5 + systemd.directives7 + systemd.special7 + systemd-oomd.service8 + The documentation for control groups and specific controllers in the Linux kernel: + Control Groups v2 + -- cgit v1.2.3