diff options
| author | Peter Morrow <pemorrow@linux.microsoft.com> | 2021-09-14 17:28:46 +0100 |
|---|---|---|
| committer | Peter Morrow <pemorrow@linux.microsoft.com> | 2021-09-15 09:52:12 +0100 |
| commit | c93a7d4ad303210541634ee95c78d186b27e1118 (patch) | |
| tree | 88a787c4fe92e5dec93d77bacdb20f7ea37764bf /man/systemd.resource-control.xml | |
| parent | 31d3a520297980ac31186e27396a05f928fde49f (diff) | |
| download | systemd-c93a7d4ad303210541634ee95c78d186b27e1118.tar.gz | |
docs: update docs with StartupAllowedCPUs and StartupAllowedMemoryNodes details
Signed-off-by: Peter Morrow <pemorrow@linux.microsoft.com>
Diffstat (limited to 'man/systemd.resource-control.xml')
| -rw-r--r-- | man/systemd.resource-control.xml | 23 |
1 files changed, 18 insertions, 5 deletions
diff --git a/man/systemd.resource-control.xml b/man/systemd.resource-control.xml index a8c8fad9ef..ea728dff33 100644 --- a/man/systemd.resource-control.xml +++ b/man/systemd.resource-control.xml @@ -237,13 +237,20 @@ <varlistentry> <term><varname>AllowedCPUs=</varname></term> + <term><varname>StartupAllowedCPUs=</varname></term> <listitem> <para>Restrict processes to be executed on specific CPUs. Takes a list of CPU indices or ranges separated by either whitespace or commas. CPU ranges are specified by the lower and upper CPU indices separated by a dash.</para> - <para>Setting <varname>AllowedCPUs=</varname> doesn't guarantee that all of the CPUs will be used by the processes - as it may be limited by parent units. The effective configuration is reported as <varname>EffectiveCPUs=</varname>.</para> + <para>Setting <varname>AllowedCPUs=</varname> or <varname>StartupAllowedCPUs=</varname> doesn't guarantee that all + of the CPUs will be used by the processes as it may be limited by parent units. The effective configuration is + reported as <varname>EffectiveCPUs=</varname>.</para> + + <para>While <varname>StartupAllowedCPUs=</varname> only applies to the startup phase of the system, + <varname>AllowedCPUs=</varname> applies to normal runtime of the system, and if the former is not set also to + the startup phase. Using <varname>StartupAllowedCPUs=</varname> allows prioritizing specific services at + boot-up differently than during normal runtime.</para> <para>This setting is supported only with the unified control group hierarchy.</para> </listitem> @@ -251,15 +258,21 @@ <varlistentry> <term><varname>AllowedMemoryNodes=</varname></term> + <term><varname>StartupAllowedMemoryNodes=</varname></term> <listitem> <para>Restrict processes to be executed on specific memory NUMA nodes. Takes a list of memory NUMA nodes indices or ranges separated by either whitespace or commas. Memory NUMA nodes ranges are specified by the lower and upper NUMA nodes indices separated by a dash.</para> - <para>Setting <varname>AllowedMemoryNodes=</varname> doesn't guarantee that all of the memory NUMA nodes will - be used by the processes as it may be limited by parent units. The effective configuration is reported as - <varname>EffectiveMemoryNodes=</varname>.</para> + <para>Setting <varname>AllowedMemoryNodes=</varname> or <varname>StartupAllowedMemoryNodes=</varname> doesn't + guarantee that all of the memory NUMA nodes will be used by the processes as it may be limited by parent units. + The effective configuration is reported as <varname>EffectiveMemoryNodes=</varname>.</para> + + <para>While <varname>StartupAllowedMemoryNodes=</varname> only applies to the startup phase of the system, + <varname>AllowedMemoryNodes=</varname> applies to normal runtime of the system, and if the former is not set also to + the startup phase. Using <varname>StartupAllowedMemoryNodes=</varname> allows prioritizing specific services at + boot-up differently than during normal runtime.</para> <para>This setting is supported only with the unified control group hierarchy.</para> </listitem> |