]>
Commit | Line | Data |
---|---|---|
3802a3d3 | 1 | <?xml version='1.0'?> <!--*- Mode: nxml; nxml-child-indent: 2; indent-tabs-mode: nil -*--> |
d868475a | 2 | <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" |
12b42c76 | 3 | "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> |
d868475a ZJS |
4 | |
5 | <!-- | |
b975b0d5 | 6 | This file is part of systemd. |
d868475a | 7 | |
b975b0d5 | 8 | Copyright 2013 Zbigniew Jędrzejewski-Szmek |
d868475a | 9 | |
b975b0d5 ZJS |
10 | systemd is free software; you can redistribute it and/or modify it |
11 | under the terms of the GNU Lesser General Public License as published by | |
12 | the Free Software Foundation; either version 2.1 of the License, or | |
13 | (at your option) any later version. | |
d868475a | 14 | |
b975b0d5 ZJS |
15 | systemd is distributed in the hope that it will be useful, but |
16 | WITHOUT ANY WARRANTY; without even the implied warranty of | |
17 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU | |
18 | Lesser General Public License for more details. | |
d868475a | 19 | |
b975b0d5 ZJS |
20 | You should have received a copy of the GNU Lesser General Public License |
21 | along with systemd; If not, see <http://www.gnu.org/licenses/>. | |
d868475a ZJS |
22 | --> |
23 | ||
3fde5f30 | 24 | <refentry id="systemd.resource-control"> |
d868475a | 25 | <refentryinfo> |
3fde5f30 | 26 | <title>systemd.resource-control</title> |
d868475a ZJS |
27 | <productname>systemd</productname> |
28 | ||
29 | <authorgroup> | |
30 | <author> | |
31 | <contrib>Developer</contrib> | |
32 | <firstname>Lennart</firstname> | |
33 | <surname>Poettering</surname> | |
34 | <email>lennart@poettering.net</email> | |
35 | </author> | |
36 | </authorgroup> | |
37 | </refentryinfo> | |
38 | ||
39 | <refmeta> | |
3fde5f30 | 40 | <refentrytitle>systemd.resource-control</refentrytitle> |
d868475a ZJS |
41 | <manvolnum>5</manvolnum> |
42 | </refmeta> | |
43 | ||
44 | <refnamediv> | |
3fde5f30 LP |
45 | <refname>systemd.resource-control</refname> |
46 | <refpurpose>Resource control unit settings</refpurpose> | |
d868475a ZJS |
47 | </refnamediv> |
48 | ||
49 | <refsynopsisdiv> | |
50 | <para> | |
51 | <filename><replaceable>slice</replaceable>.slice</filename>, | |
52 | <filename><replaceable>scope</replaceable>.scope</filename>, | |
53 | <filename><replaceable>service</replaceable>.service</filename>, | |
54 | <filename><replaceable>socket</replaceable>.socket</filename>, | |
55 | <filename><replaceable>mount</replaceable>.mount</filename>, | |
56 | <filename><replaceable>swap</replaceable>.swap</filename> | |
57 | </para> | |
58 | </refsynopsisdiv> | |
59 | ||
60 | <refsect1> | |
61 | <title>Description</title> | |
62 | ||
c7458f93 LP |
63 | <para>Unit configuration files for services, slices, scopes, sockets, mount points, and swap devices share a subset |
64 | of configuration options for resource control of spawned processes. Internally, this relies on the Linux Control | |
65 | Groups (cgroups) kernel concept for organizing processes in a hierarchical tree of named groups for the purpose of | |
66 | resource management.</para> | |
9365b048 | 67 | |
d868475a ZJS |
68 | <para>This man page lists the configuration options shared by |
69 | those six unit types. See | |
70 | <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry> | |
71 | for the common options of all unit configuration files, and | |
72 | <citerefentry><refentrytitle>systemd.slice</refentrytitle><manvolnum>5</manvolnum></citerefentry>, | |
73 | <citerefentry><refentrytitle>systemd.scope</refentrytitle><manvolnum>5</manvolnum></citerefentry>, | |
74 | <citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>, | |
75 | <citerefentry><refentrytitle>systemd.socket</refentrytitle><manvolnum>5</manvolnum></citerefentry>, | |
76 | <citerefentry><refentrytitle>systemd.mount</refentrytitle><manvolnum>5</manvolnum></citerefentry>, | |
77 | and | |
78 | <citerefentry><refentrytitle>systemd.swap</refentrytitle><manvolnum>5</manvolnum></citerefentry> | |
79 | for more information on the specific unit configuration files. The | |
3fde5f30 | 80 | resource control configuration options are configured in the |
d868475a ZJS |
81 | [Slice], [Scope], [Service], [Socket], [Mount], or [Swap] |
82 | sections, depending on the unit type.</para> | |
ea021cc3 | 83 | |
74b47bbd ZJS |
84 | <para>In addition, options which control resources available to programs |
85 | <emphasis>executed</emphasis> by systemd are listed in | |
86 | <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>. | |
87 | Those options complement options listed here.</para> | |
88 | ||
ea021cc3 | 89 | <para>See the <ulink |
28a0ad81 | 90 | url="https://www.freedesktop.org/wiki/Software/systemd/ControlGroupInterface/">New |
72f4d966 | 91 | Control Group Interfaces</ulink> for an introduction on how to make |
ea021cc3 | 92 | use of resource control APIs from programs.</para> |
d868475a ZJS |
93 | </refsect1> |
94 | ||
c129bd5d | 95 | <refsect1> |
45f09f93 | 96 | <title>Implicit Dependencies</title> |
c129bd5d | 97 | |
45f09f93 JL |
98 | <para>The following dependencies are implicitly added:</para> |
99 | ||
100 | <itemizedlist> | |
101 | <listitem><para>Units with the <varname>Slice=</varname> setting set automatically acquire | |
102 | <varname>Requires=</varname> and <varname>After=</varname> dependencies on the specified | |
103 | slice unit.</para></listitem> | |
104 | </itemizedlist> | |
c129bd5d LP |
105 | </refsect1> |
106 | ||
45f09f93 JL |
107 | <!-- We don't have any default dependency here. --> |
108 | ||
538b4852 TH |
109 | <refsect1> |
110 | <title>Unified and Legacy Control Group Hierarchies</title> | |
111 | ||
65c1cdb2 MR |
112 | <para>The unified control group hierarchy is the new version of kernel control group interface, see <ulink |
113 | url="https://www.kernel.org/doc/Documentation/cgroup-v2.txt">cgroup-v2.txt</ulink>. Depending on the resource type, | |
114 | there are differences in resource control capabilities. Also, because of interface changes, some resource types | |
115 | have separate set of options on the unified hierarchy.</para> | |
538b4852 TH |
116 | |
117 | <para> | |
118 | <variablelist> | |
66ebf6c0 | 119 | |
538b4852 | 120 | <varlistentry> |
66ebf6c0 | 121 | <term><option>CPU</option></term> |
538b4852 | 122 | <listitem> |
66ebf6c0 | 123 | <para>Due to the lack of consensus in the kernel community, the CPU controller support on the unified |
c7458f93 | 124 | control group hierarchy requires out-of-tree kernel patches. See <ulink |
66ebf6c0 TH |
125 | url="https://git.kernel.org/cgit/linux/kernel/git/tj/cgroup.git/tree/Documentation/cgroup-v2-cpu.txt?h=cgroup-v2-cpu">cgroup-v2-cpu.txt</ulink>.</para> |
126 | ||
127 | <para><varname>CPUWeight=</varname> and <varname>StartupCPUWeight=</varname> replace | |
128 | <varname>CPUShares=</varname> and <varname>StartupCPUShares=</varname>, respectively.</para> | |
129 | ||
130 | <para>The <literal>cpuacct</literal> controller does not exist separately on the unified hierarchy.</para> | |
538b4852 TH |
131 | </listitem> |
132 | </varlistentry> | |
66ebf6c0 | 133 | |
da4d897e TH |
134 | <varlistentry> |
135 | <term><option>Memory</option></term> | |
136 | <listitem> | |
328583db LP |
137 | <para><varname>MemoryMax=</varname> replaces <varname>MemoryLimit=</varname>. <varname>MemoryLow=</varname> |
138 | and <varname>MemoryHigh=</varname> are effective only on unified hierarchy.</para> | |
da4d897e TH |
139 | </listitem> |
140 | </varlistentry> | |
66ebf6c0 TH |
141 | |
142 | <varlistentry> | |
143 | <term><option>IO</option></term> | |
144 | <listitem> | |
145 | <para><varname>IO</varname> prefixed settings are superset of and replace <varname>BlockIO</varname> | |
146 | prefixed ones. On unified hierarchy, IO resource control also applies to buffered writes.</para> | |
147 | </listitem> | |
148 | </varlistentry> | |
149 | ||
538b4852 TH |
150 | </variablelist> |
151 | </para> | |
152 | ||
7d862ab8 TH |
153 | <para>To ease the transition, there is best-effort translation between the two versions of settings. For each |
154 | controller, if any of the settings for the unified hierarchy are present, all settings for the legacy hierarchy are | |
155 | ignored. If the resulting settings are for the other type of hierarchy, the configurations are translated before | |
156 | application.</para> | |
c23b2c70 MR |
157 | |
158 | <para>Legacy control group hierarchy (see <ulink | |
159 | url="https://www.kernel.org/doc/Documentation/cgroup-v1/cgroups.txt">cgroups.txt</ulink>), also called cgroup-v1, | |
0d5299ef | 160 | doesn't allow safe delegation of controllers to unprivileged processes. If the system uses the legacy control group |
c23b2c70 MR |
161 | hierarchy, resource control is disabled for systemd user instance, see |
162 | <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>. | |
163 | </para> | |
538b4852 TH |
164 | </refsect1> |
165 | ||
d868475a ZJS |
166 | <refsect1> |
167 | <title>Options</title> | |
168 | ||
169 | <para>Units of the types listed above can have settings | |
3fde5f30 | 170 | for resource control configuration:</para> |
d868475a ZJS |
171 | |
172 | <variablelist class='unit-directives'> | |
d868475a ZJS |
173 | |
174 | <varlistentry> | |
61ad59b1 | 175 | <term><varname>CPUAccounting=</varname></term> |
d868475a ZJS |
176 | |
177 | <listitem> | |
61ad59b1 LP |
178 | <para>Turn on CPU usage accounting for this unit. Takes a |
179 | boolean argument. Note that turning on CPU accounting for | |
03a7b521 | 180 | one unit will also implicitly turn it on for all units |
085afe36 LP |
181 | contained in the same slice and for all its parent slices |
182 | and the units contained therein. The system default for this | |
03a7b521 | 183 | setting may be controlled with |
085afe36 LP |
184 | <varname>DefaultCPUAccounting=</varname> in |
185 | <citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para> | |
d868475a ZJS |
186 | </listitem> |
187 | </varlistentry> | |
188 | ||
66ebf6c0 TH |
189 | <varlistentry> |
190 | <term><varname>CPUWeight=<replaceable>weight</replaceable></varname></term> | |
191 | <term><varname>StartupCPUWeight=<replaceable>weight</replaceable></varname></term> | |
192 | ||
193 | <listitem> | |
194 | <para>Assign the specified CPU time weight to the processes executed, if the unified control group hierarchy | |
195 | is used on the system. These options take an integer value and control the <literal>cpu.weight</literal> | |
196 | control group attribute. The allowed range is 1 to 10000. Defaults to 100. For details about this control | |
197 | group attribute, see <ulink | |
198 | url="https://www.kernel.org/doc/Documentation/cgroup-v2.txt">cgroup-v2.txt</ulink> and <ulink | |
199 | url="https://www.kernel.org/doc/Documentation/scheduler/sched-design-CFS.txt">sched-design-CFS.txt</ulink>. | |
200 | The available CPU time is split up among all units within one slice relative to their CPU time weight.</para> | |
201 | ||
202 | <para>While <varname>StartupCPUWeight=</varname> only applies to the startup phase of the system, | |
203 | <varname>CPUWeight=</varname> applies to normal runtime of the system, and if the former is not set also to | |
204 | the startup phase. Using <varname>StartupCPUWeight=</varname> allows prioritizing specific services at | |
205 | boot-up differently than during normal runtime.</para> | |
206 | ||
207 | <para>Implies <literal>CPUAccounting=true</literal>.</para> | |
208 | ||
7d862ab8 | 209 | <para>These settings replace <varname>CPUShares=</varname> and <varname>StartupCPUShares=</varname>.</para> |
b2f8b02e LP |
210 | </listitem> |
211 | </varlistentry> | |
212 | ||
213 | <varlistentry> | |
214 | <term><varname>CPUQuota=</varname></term> | |
215 | ||
216 | <listitem> | |
66ebf6c0 TH |
217 | <para>Assign the specified CPU time quota to the processes executed. Takes a percentage value, suffixed with |
218 | "%". The percentage specifies how much CPU time the unit shall get at maximum, relative to the total CPU time | |
219 | available on one CPU. Use values > 100% for allotting CPU time on more than one CPU. This controls the | |
220 | <literal>cpu.max</literal> attribute on the unified control group hierarchy and | |
221 | <literal>cpu.cfs_quota_us</literal> on legacy. For details about these control group attributes, see <ulink | |
222 | url="https://www.kernel.org/doc/Documentation/cgroup-v2.txt">cgroup-v2.txt</ulink> and <ulink | |
b2f8b02e LP |
223 | url="https://www.kernel.org/doc/Documentation/scheduler/sched-design-CFS.txt">sched-design-CFS.txt</ulink>.</para> |
224 | ||
66ebf6c0 TH |
225 | <para>Example: <varname>CPUQuota=20%</varname> ensures that the executed processes will never get more than |
226 | 20% CPU time on one CPU.</para> | |
b2f8b02e LP |
227 | |
228 | <para>Implies <literal>CPUAccounting=true</literal>.</para> | |
229 | </listitem> | |
230 | </varlistentry> | |
231 | ||
61ad59b1 LP |
232 | <varlistentry> |
233 | <term><varname>MemoryAccounting=</varname></term> | |
234 | ||
235 | <listitem> | |
236 | <para>Turn on process and kernel memory accounting for this | |
237 | unit. Takes a boolean argument. Note that turning on memory | |
03a7b521 LP |
238 | accounting for one unit will also implicitly turn it on for |
239 | all units contained in the same slice and for all its parent | |
240 | slices and the units contained therein. The system default | |
241 | for this setting may be controlled with | |
085afe36 LP |
242 | <varname>DefaultMemoryAccounting=</varname> in |
243 | <citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para> | |
61ad59b1 LP |
244 | </listitem> |
245 | </varlistentry> | |
246 | ||
da4d897e TH |
247 | <varlistentry> |
248 | <term><varname>MemoryLow=<replaceable>bytes</replaceable></varname></term> | |
249 | ||
250 | <listitem> | |
251 | <para>Specify the best-effort memory usage protection of the executed processes in this unit. If the memory | |
252 | usages of this unit and all its ancestors are below their low boundaries, this unit's memory won't be | |
253 | reclaimed as long as memory can be reclaimed from unprotected units.</para> | |
254 | ||
255 | <para>Takes a memory size in bytes. If the value is suffixed with K, M, G or T, the specified memory size is | |
875ae566 LP |
256 | parsed as Kilobytes, Megabytes, Gigabytes, or Terabytes (with the base 1024), respectively. Alternatively, a |
257 | percentage value may be specified, which is taken relative to the installed physical memory on the | |
258 | system. This controls the <literal>memory.low</literal> control group attribute. For details about this | |
259 | control group attribute, see <ulink | |
260 | url="https://www.kernel.org/doc/Documentation/cgroup-v2.txt">cgroup-v2.txt</ulink>.</para> | |
da4d897e TH |
261 | |
262 | <para>Implies <literal>MemoryAccounting=true</literal>.</para> | |
263 | ||
7d862ab8 TH |
264 | <para>This setting is supported only if the unified control group hierarchy is used and disables |
265 | <varname>MemoryLimit=</varname>.</para> | |
da4d897e TH |
266 | </listitem> |
267 | </varlistentry> | |
268 | ||
269 | <varlistentry> | |
270 | <term><varname>MemoryHigh=<replaceable>bytes</replaceable></varname></term> | |
271 | ||
272 | <listitem> | |
273 | <para>Specify the high limit on memory usage of the executed processes in this unit. Memory usage may go | |
274 | above the limit if unavoidable, but the processes are heavily slowed down and memory is taken away | |
275 | aggressively in such cases. This is the main mechanism to control memory usage of a unit.</para> | |
276 | ||
277 | <para>Takes a memory size in bytes. If the value is suffixed with K, M, G or T, the specified memory size is | |
875ae566 LP |
278 | parsed as Kilobytes, Megabytes, Gigabytes, or Terabytes (with the base 1024), respectively. Alternatively, a |
279 | percentage value may be specified, which is taken relative to the installed physical memory on the | |
280 | system. If assigned the | |
e57c9ce1 | 281 | special value <literal>infinity</literal>, no memory limit is applied. This controls the |
da4d897e TH |
282 | <literal>memory.high</literal> control group attribute. For details about this control group attribute, see |
283 | <ulink url="https://www.kernel.org/doc/Documentation/cgroup-v2.txt">cgroup-v2.txt</ulink>.</para> | |
284 | ||
285 | <para>Implies <literal>MemoryAccounting=true</literal>.</para> | |
286 | ||
7d862ab8 TH |
287 | <para>This setting is supported only if the unified control group hierarchy is used and disables |
288 | <varname>MemoryLimit=</varname>.</para> | |
da4d897e TH |
289 | </listitem> |
290 | </varlistentry> | |
291 | ||
292 | <varlistentry> | |
293 | <term><varname>MemoryMax=<replaceable>bytes</replaceable></varname></term> | |
294 | ||
295 | <listitem> | |
296 | <para>Specify the absolute limit on memory usage of the executed processes in this unit. If memory usage | |
297 | cannot be contained under the limit, out-of-memory killer is invoked inside the unit. It is recommended to | |
298 | use <varname>MemoryHigh=</varname> as the main control mechanism and use <varname>MemoryMax=</varname> as the | |
299 | last line of defense.</para> | |
300 | ||
301 | <para>Takes a memory size in bytes. If the value is suffixed with K, M, G or T, the specified memory size is | |
875ae566 LP |
302 | parsed as Kilobytes, Megabytes, Gigabytes, or Terabytes (with the base 1024), respectively. Alternatively, a |
303 | percentage value may be specified, which is taken relative to the installed physical memory on the system. If | |
304 | assigned the special value <literal>infinity</literal>, no memory limit is applied. This controls the | |
da4d897e TH |
305 | <literal>memory.max</literal> control group attribute. For details about this control group attribute, see |
306 | <ulink url="https://www.kernel.org/doc/Documentation/cgroup-v2.txt">cgroup-v2.txt</ulink>.</para> | |
307 | ||
308 | <para>Implies <literal>MemoryAccounting=true</literal>.</para> | |
309 | ||
7d862ab8 | 310 | <para>This setting replaces <varname>MemoryLimit=</varname>.</para> |
da4d897e TH |
311 | </listitem> |
312 | </varlistentry> | |
313 | ||
96e131ea WC |
314 | <varlistentry> |
315 | <term><varname>MemorySwapMax=<replaceable>bytes</replaceable></varname></term> | |
316 | ||
317 | <listitem> | |
318 | <para>Specify the absolute limit on swap usage of the executed processes in this unit.</para> | |
319 | ||
320 | <para>Takes a swap size in bytes. If the value is suffixed with K, M, G or T, the specified swap size is | |
321 | parsed as Kilobytes, Megabytes, Gigabytes, or Terabytes (with the base 1024), respectively. If assigned the | |
322 | special value <literal>infinity</literal>, no swap limit is applied. This controls the | |
323 | <literal>memory.swap.max</literal> control group attribute. For details about this control group attribute, | |
324 | see <ulink url="https://www.kernel.org/doc/Documentation/cgroup-v2.txt">cgroup-v2.txt</ulink>.</para> | |
325 | ||
326 | <para>Implies <literal>MemoryAccounting=true</literal>.</para> | |
327 | ||
7d862ab8 TH |
328 | <para>This setting is supported only if the unified control group hierarchy is used and disables |
329 | <varname>MemoryLimit=</varname>.</para> | |
d868475a ZJS |
330 | </listitem> |
331 | </varlistentry> | |
332 | ||
03a7b521 LP |
333 | <varlistentry> |
334 | <term><varname>TasksAccounting=</varname></term> | |
335 | ||
336 | <listitem> | |
337 | <para>Turn on task accounting for this unit. Takes a | |
338 | boolean argument. If enabled, the system manager will keep | |
339 | track of the number of tasks in the unit. The number of | |
340 | tasks accounted this way includes both kernel threads and | |
341 | userspace processes, with each thread counting | |
342 | individually. Note that turning on tasks accounting for one | |
343 | unit will also implicitly turn it on for all units contained | |
344 | in the same slice and for all its parent slices and the | |
345 | units contained therein. The system default for this setting | |
346 | may be controlled with | |
347 | <varname>DefaultTasksAccounting=</varname> in | |
348 | <citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para> | |
349 | </listitem> | |
350 | </varlistentry> | |
351 | ||
352 | <varlistentry> | |
353 | <term><varname>TasksMax=<replaceable>N</replaceable></varname></term> | |
354 | ||
355 | <listitem> | |
83f8e808 LP |
356 | <para>Specify the maximum number of tasks that may be created in the unit. This ensures that the number of |
357 | tasks accounted for the unit (see above) stays below a specific limit. This either takes an absolute number | |
358 | of tasks or a percentage value that is taken relative to the configured maximum number of tasks on the | |
359 | system. If assigned the special value <literal>infinity</literal>, no tasks limit is applied. This controls | |
360 | the <literal>pids.max</literal> control group attribute. For details about this control group attribute, see | |
361 | <ulink url="https://www.kernel.org/doc/Documentation/cgroup-v1/pids.txt">pids.txt</ulink>.</para> | |
03a7b521 | 362 | |
0af20ea2 LP |
363 | <para>Implies <literal>TasksAccounting=true</literal>. The |
364 | system default for this setting may be controlled with | |
365 | <varname>DefaultTasksMax=</varname> in | |
366 | <citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para> | |
03a7b521 LP |
367 | </listitem> |
368 | </varlistentry> | |
369 | ||
13c31542 TH |
370 | <varlistentry> |
371 | <term><varname>IOAccounting=</varname></term> | |
372 | ||
373 | <listitem> | |
0069a0dd LP |
374 | <para>Turn on Block I/O accounting for this unit, if the unified control group hierarchy is used on the |
375 | system. Takes a boolean argument. Note that turning on block I/O accounting for one unit will also implicitly | |
376 | turn it on for all units contained in the same slice and all for its parent slices and the units contained | |
377 | therein. The system default for this setting may be controlled with <varname>DefaultIOAccounting=</varname> | |
378 | in | |
13c31542 | 379 | <citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para> |
0069a0dd | 380 | |
7d862ab8 TH |
381 | <para>This setting replaces <varname>BlockIOAccounting=</varname> and disables settings prefixed with |
382 | <varname>BlockIO</varname> or <varname>StartupBlockIO</varname>.</para> | |
13c31542 TH |
383 | </listitem> |
384 | </varlistentry> | |
385 | ||
386 | <varlistentry> | |
387 | <term><varname>IOWeight=<replaceable>weight</replaceable></varname></term> | |
388 | <term><varname>StartupIOWeight=<replaceable>weight</replaceable></varname></term> | |
389 | ||
390 | <listitem> | |
0069a0dd LP |
391 | <para>Set the default overall block I/O weight for the executed processes, if the unified control group |
392 | hierarchy is used on the system. Takes a single weight value (between 1 and 10000) to set the default block | |
393 | I/O weight. This controls the <literal>io.weight</literal> control group attribute, which defaults to | |
394 | 100. For details about this control group attribute, see <ulink | |
395 | url="https://www.kernel.org/doc/Documentation/cgroup-v2.txt">cgroup-v2.txt</ulink>. The available I/O | |
396 | bandwidth is split up among all units within one slice relative to their block I/O weight.</para> | |
13c31542 TH |
397 | |
398 | <para>While <varname>StartupIOWeight=</varname> only applies | |
399 | to the startup phase of the system, | |
400 | <varname>IOWeight=</varname> applies to the later runtime of | |
401 | the system, and if the former is not set also to the startup | |
402 | phase. This allows prioritizing specific services at boot-up | |
403 | differently than during runtime.</para> | |
404 | ||
405 | <para>Implies <literal>IOAccounting=true</literal>.</para> | |
0069a0dd | 406 | |
7d862ab8 TH |
407 | <para>These settings replace <varname>BlockIOWeight=</varname> and <varname>StartupBlockIOWeight=</varname> |
408 | and disable settings prefixed with <varname>BlockIO</varname> or <varname>StartupBlockIO</varname>.</para> | |
13c31542 TH |
409 | </listitem> |
410 | </varlistentry> | |
411 | ||
412 | <varlistentry> | |
413 | <term><varname>IODeviceWeight=<replaceable>device</replaceable> <replaceable>weight</replaceable></varname></term> | |
414 | ||
415 | <listitem> | |
0069a0dd LP |
416 | <para>Set the per-device overall block I/O weight for the executed processes, if the unified control group |
417 | hierarchy is used on the system. Takes a space-separated pair of a file path and a weight value to specify | |
418 | the device specific weight value, between 1 and 10000. (Example: "/dev/sda 1000"). The file path may be | |
419 | specified as path to a block device node or as any other file, in which case the backing block device of the | |
420 | file system of the file is determined. This controls the <literal>io.weight</literal> control group | |
421 | attribute, which defaults to 100. Use this option multiple times to set weights for multiple devices. For | |
422 | details about this control group attribute, see <ulink | |
13c31542 TH |
423 | url="https://www.kernel.org/doc/Documentation/cgroup-v2.txt">cgroup-v2.txt</ulink>.</para> |
424 | ||
425 | <para>Implies <literal>IOAccounting=true</literal>.</para> | |
0069a0dd | 426 | |
7d862ab8 TH |
427 | <para>This setting replaces <varname>BlockIODeviceWeight=</varname> and disables settings prefixed with |
428 | <varname>BlockIO</varname> or <varname>StartupBlockIO</varname>.</para> | |
13c31542 TH |
429 | </listitem> |
430 | </varlistentry> | |
431 | ||
432 | <varlistentry> | |
433 | <term><varname>IOReadBandwidthMax=<replaceable>device</replaceable> <replaceable>bytes</replaceable></varname></term> | |
434 | <term><varname>IOWriteBandwidthMax=<replaceable>device</replaceable> <replaceable>bytes</replaceable></varname></term> | |
435 | ||
436 | <listitem> | |
0069a0dd LP |
437 | <para>Set the per-device overall block I/O bandwidth maximum limit for the executed processes, if the unified |
438 | control group hierarchy is used on the system. This limit is not work-conserving and the executed processes | |
439 | are not allowed to use more even if the device has idle capacity. Takes a space-separated pair of a file | |
440 | path and a bandwidth value (in bytes per second) to specify the device specific bandwidth. The file path may | |
441 | be a path to a block device node, or as any other file in which case the backing block device of the file | |
442 | system of the file is used. If the bandwidth is suffixed with K, M, G, or T, the specified bandwidth is | |
443 | parsed as Kilobytes, Megabytes, Gigabytes, or Terabytes, respectively, to the base of 1000. (Example: | |
444 | "/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0 5M"). This controls the <literal>io.max</literal> control | |
445 | group attributes. Use this option multiple times to set bandwidth limits for multiple devices. For details | |
446 | about this control group attribute, see <ulink | |
13c31542 TH |
447 | url="https://www.kernel.org/doc/Documentation/cgroup-v2.txt">cgroup-v2.txt</ulink>. |
448 | </para> | |
449 | ||
450 | <para>Implies <literal>IOAccounting=true</literal>.</para> | |
0069a0dd | 451 | |
7d862ab8 TH |
452 | <para>These settings replace <varname>BlockIOReadBandwidth=</varname> and |
453 | <varname>BlockIOWriteBandwidth=</varname> and disable settings prefixed with <varname>BlockIO</varname> or | |
454 | <varname>StartupBlockIO</varname>.</para> | |
13c31542 TH |
455 | </listitem> |
456 | </varlistentry> | |
457 | ||
ac06a0cf TH |
458 | <varlistentry> |
459 | <term><varname>IOReadIOPSMax=<replaceable>device</replaceable> <replaceable>IOPS</replaceable></varname></term> | |
460 | <term><varname>IOWriteIOPSMax=<replaceable>device</replaceable> <replaceable>IOPS</replaceable></varname></term> | |
461 | ||
462 | <listitem> | |
463 | <para>Set the per-device overall block I/O IOs-Per-Second maximum limit for the executed processes, if the | |
464 | unified control group hierarchy is used on the system. This limit is not work-conserving and the executed | |
465 | processes are not allowed to use more even if the device has idle capacity. Takes a space-separated pair of | |
466 | a file path and an IOPS value to specify the device specific IOPS. The file path may be a path to a block | |
467 | device node, or as any other file in which case the backing block device of the file system of the file is | |
468 | used. If the IOPS is suffixed with K, M, G, or T, the specified IOPS is parsed as KiloIOPS, MegaIOPS, | |
469 | GigaIOPS, or TeraIOPS, respectively, to the base of 1000. (Example: | |
470 | "/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0 1K"). This controls the <literal>io.max</literal> control | |
471 | group attributes. Use this option multiple times to set IOPS limits for multiple devices. For details about | |
472 | this control group attribute, see <ulink | |
473 | url="https://www.kernel.org/doc/Documentation/cgroup-v2.txt">cgroup-v2.txt</ulink>. | |
474 | </para> | |
475 | ||
476 | <para>Implies <literal>IOAccounting=true</literal>.</para> | |
477 | ||
7d862ab8 TH |
478 | <para>These settings are supported only if the unified control group hierarchy is used and disable settings |
479 | prefixed with <varname>BlockIO</varname> or <varname>StartupBlockIO</varname>.</para> | |
d868475a ZJS |
480 | </listitem> |
481 | </varlistentry> | |
482 | ||
8d8631d4 DM |
483 | <varlistentry> |
484 | <term><varname>IPAccounting=</varname></term> | |
485 | ||
486 | <listitem> | |
487 | <para>Takes a boolean argument. If true, turns on IPv4 and IPv6 network traffic accounting for packets sent | |
488 | or received by the unit. When this option is turned on, all IPv4 and IPv6 sockets created by any process of | |
489 | the unit are accounted for. When this option is used in socket units, it applies to all IPv4 and IPv6 sockets | |
490 | associated with it (including both listening and connection sockets where this applies). Note that for | |
491 | socket-activated services, this configuration setting and the accounting data of the service unit and the | |
492 | socket unit are kept separate, and displayed separately. No propagation of the setting and the collected | |
493 | statistics is done, in either direction. Moreover, any traffic sent or received on any of the socket unit's | |
494 | sockets is accounted to the socket unit — and never to the service unit it might have activated, even if the | |
495 | socket is used by it. Note that IP accounting is currently not supported for slice units, and enabling this | |
496 | option for them has no effect. The system default for this setting may be controlled with | |
497 | <varname>DefaultIPAccounting=</varname> in | |
498 | <citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para> | |
499 | </listitem> | |
500 | </varlistentry> | |
501 | ||
502 | <varlistentry> | |
dcfaecc7 | 503 | <term><varname>IPAddressAllow=<replaceable>ADDRESS[/PREFIXLENGTH]…</replaceable></varname></term> |
8d8631d4 DM |
504 | <term><varname>IPAddressDeny=<replaceable>ADDRESS[/PREFIXLENGTH]…</replaceable></varname></term> |
505 | ||
506 | <listitem> | |
507 | <para>Turn on address range network traffic filtering for packets sent and received over AF_INET and AF_INET6 | |
508 | sockets. Both directives take a space separated list of IPv4 or IPv6 addresses, each optionally suffixed | |
509 | with an address prefix length (separated by a <literal>/</literal> character). If the latter is omitted, the | |
510 | address is considered a host address, i.e. the prefix covers the whole address (32 for IPv4, 128 for IPv6). | |
511 | </para> | |
512 | ||
513 | <para>The access lists configured with this option are applied to all sockets created by processes of this | |
514 | unit (or in the case of socket units, associated with it). The lists are implicitly combined with any lists | |
515 | configured for any of the parent slice units this unit might be a member of. By default all access lists are | |
516 | empty. When configured the lists are enforced as follows:</para> | |
517 | ||
518 | <itemizedlist> | |
519 | <listitem><para>Access will be granted in case its destination/source address matches any entry in the | |
520 | <varname>IPAddressAllow=</varname> setting.</para></listitem> | |
521 | ||
522 | <listitem><para>Otherwise, access will be denied in case its destination/source address matches any entry | |
523 | in the <varname>IPAddressDeny=</varname> setting.</para></listitem> | |
524 | ||
525 | <listitem><para>Otherwise, access will be granted.</para></listitem> | |
526 | </itemizedlist> | |
527 | ||
528 | <para>In order to implement a whitelisting IP firewall, it is recommended to use a | |
529 | <varname>IPAddressDeny=</varname><constant>any</constant> setting on an upper-level slice unit (such as the | |
530 | root slice <filename>-.slice</filename> or the slice containing all system services | |
531 | <filename>system.slice</filename> – see | |
532 | <citerefentry><refentrytitle>systemd.special</refentrytitle><manvolnum>7</manvolnum></citerefentry> for | |
533 | details on these slice units), plus individual per-service <varname>IPAddressAllow=</varname> lines | |
534 | permitting network access to relevant services, and only them.</para> | |
535 | ||
536 | <para>Note that for socket-activated services, the IP access list configured on the socket unit applies to | |
537 | all sockets associated with it directly, but not to any sockets created by the ultimately activated services | |
538 | for it. Conversely, the IP access list configured for the service is not applied to any sockets passed into | |
539 | the service via socket activation. Thus, it is usually a good idea, to replicate the IP access lists on both | |
540 | the socket and the service unit, however it often makes sense to maintain one list more open and the other | |
541 | one more restricted, depending on the usecase.</para> | |
542 | ||
543 | <para>If these settings are used multiple times in the same unit the specified lists are combined. If an | |
544 | empty string is assigned to these settings the specific access list is reset and all previous settings undone.</para> | |
545 | ||
546 | <para>In place of explicit IPv4 or IPv6 address and prefix length specifications a small set of symbolic | |
547 | names may be used. The following names are defined:</para> | |
548 | ||
549 | <table> | |
550 | <title>Special address/network names</title> | |
551 | ||
552 | <tgroup cols='3'> | |
553 | <colspec colname='name'/> | |
554 | <colspec colname='definition'/> | |
555 | <colspec colname='meaning'/> | |
556 | ||
557 | <thead> | |
558 | <row> | |
559 | <entry>Symbolic Name</entry> | |
560 | <entry>Definition</entry> | |
561 | <entry>Meaning</entry> | |
562 | </row> | |
563 | </thead> | |
564 | ||
565 | <tbody> | |
566 | <row> | |
567 | <entry><constant>any</constant></entry> | |
568 | <entry>0.0.0.0/0 ::/0</entry> | |
569 | <entry>Any host</entry> | |
570 | </row> | |
571 | ||
572 | <row> | |
573 | <entry><constant>localhost</constant></entry> | |
574 | <entry>127.0.0.0/8 ::1/128</entry> | |
575 | <entry>All addresses on the local loopback</entry> | |
576 | </row> | |
577 | ||
578 | <row> | |
579 | <entry><constant>link-local</constant></entry> | |
580 | <entry>169.254.0.0/16 fe80::/64</entry> | |
581 | <entry>All link-local IP addresses</entry> | |
582 | </row> | |
583 | ||
584 | <row> | |
585 | <entry><constant>multicast</constant></entry> | |
586 | <entry>224.0.0.0/4 ff00::/8</entry> | |
587 | <entry>All IP multicasting addresses</entry> | |
588 | </row> | |
589 | </tbody> | |
590 | </tgroup> | |
591 | </table> | |
592 | ||
593 | <para>Note that these settings might not be supported on some systems (for example if eBPF control group | |
594 | support is not enabled in the underlying kernel or container manager). These settings will have no effect in | |
595 | that case. If compatibility with such systems is desired it is hence recommended to not exclusively rely on | |
596 | them for IP security.</para> | |
597 | </listitem> | |
598 | </varlistentry> | |
599 | ||
d868475a ZJS |
600 | <varlistentry> |
601 | <term><varname>DeviceAllow=</varname></term> | |
602 | ||
603 | <listitem> | |
604 | <para>Control access to specific device nodes by the | |
605 | executed processes. Takes two space-separated strings: a | |
90060676 LP |
606 | device node specifier followed by a combination of |
607 | <constant>r</constant>, <constant>w</constant>, | |
608 | <constant>m</constant> to control | |
d868475a | 609 | <emphasis>r</emphasis>eading, <emphasis>w</emphasis>riting, |
90060676 | 610 | or creation of the specific device node(s) by the unit |
d868475a ZJS |
611 | (<emphasis>m</emphasis>knod), respectively. This controls |
612 | the <literal>devices.allow</literal> and | |
613 | <literal>devices.deny</literal> control group | |
90060676 LP |
614 | attributes. For details about these control group |
615 | attributes, see <ulink | |
c51fa947 | 616 | url="https://www.kernel.org/doc/Documentation/cgroup-v1/devices.txt">devices.txt</ulink>.</para> |
90060676 LP |
617 | |
618 | <para>The device node specifier is either a path to a device | |
619 | node in the file system, starting with | |
620 | <filename>/dev/</filename>, or a string starting with either | |
621 | <literal>char-</literal> or <literal>block-</literal> | |
622 | followed by a device group name, as listed in | |
623 | <filename>/proc/devices</filename>. The latter is useful to | |
624 | whitelist all current and future devices belonging to a | |
e41969e3 | 625 | specific device group at once. The device group is matched |
1245e413 | 626 | according to filename globbing rules, you may hence use the |
e41969e3 LP |
627 | <literal>*</literal> and <literal>?</literal> |
628 | wildcards. Examples: <filename>/dev/sda5</filename> is a | |
629 | path to a device node, referring to an ATA or SCSI block | |
90060676 LP |
630 | device. <literal>char-pts</literal> and |
631 | <literal>char-alsa</literal> are specifiers for all pseudo | |
e41969e3 LP |
632 | TTYs and all ALSA sound devices, |
633 | respectively. <literal>char-cpu/*</literal> is a specifier | |
634 | matching all CPU related device groups.</para> | |
d868475a ZJS |
635 | </listitem> |
636 | </varlistentry> | |
637 | ||
638 | <varlistentry> | |
639 | <term><varname>DevicePolicy=auto|closed|strict</varname></term> | |
640 | ||
641 | <listitem> | |
642 | <para> | |
643 | Control the policy for allowing device access: | |
644 | </para> | |
645 | <variablelist> | |
646 | <varlistentry> | |
647 | <term><option>strict</option></term> | |
648 | <listitem> | |
649 | <para>means to only allow types of access that are | |
650 | explicitly specified.</para> | |
651 | </listitem> | |
652 | </varlistentry> | |
653 | ||
654 | <varlistentry> | |
655 | <term><option>closed</option></term> | |
656 | <listitem> | |
6a75304e | 657 | <para>in addition, allows access to standard pseudo |
d868475a ZJS |
658 | devices including |
659 | <filename>/dev/null</filename>, | |
660 | <filename>/dev/zero</filename>, | |
661 | <filename>/dev/full</filename>, | |
662 | <filename>/dev/random</filename>, and | |
663 | <filename>/dev/urandom</filename>. | |
664 | </para> | |
665 | </listitem> | |
666 | </varlistentry> | |
667 | ||
668 | <varlistentry> | |
669 | <term><option>auto</option></term> | |
670 | <listitem> | |
671 | <para> | |
6a75304e | 672 | in addition, allows access to all devices if no |
d868475a ZJS |
673 | explicit <varname>DeviceAllow=</varname> is present. |
674 | This is the default. | |
675 | </para> | |
676 | </listitem> | |
677 | </varlistentry> | |
678 | </variablelist> | |
679 | </listitem> | |
680 | </varlistentry> | |
61ad59b1 LP |
681 | |
682 | <varlistentry> | |
683 | <term><varname>Slice=</varname></term> | |
684 | ||
685 | <listitem> | |
686 | <para>The name of the slice unit to place the unit | |
687 | in. Defaults to <filename>system.slice</filename> for all | |
dc7adf20 LP |
688 | non-instantiated units of all unit types (except for slice |
689 | units themselves see below). Instance units are by default | |
690 | placed in a subslice of <filename>system.slice</filename> | |
691 | that is named after the template name.</para> | |
692 | ||
693 | <para>This option may be used to arrange systemd units in a | |
694 | hierarchy of slices each of which might have resource | |
695 | settings applied.</para> | |
61ad59b1 | 696 | |
fbce1139 | 697 | <para>For units of type slice, the only accepted value for |
61ad59b1 | 698 | this setting is the parent slice. Since the name of a slice |
fbce1139 | 699 | unit implies the parent slice, it is hence redundant to ever |
61ad59b1 | 700 | set this parameter directly for slice units.</para> |
ae0a5fb1 LP |
701 | |
702 | <para>Special care should be taken when relying on the default slice assignment in templated service units | |
703 | that have <varname>DefaultDependencies=no</varname> set, see | |
704 | <citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>, section | |
45f09f93 | 705 | "Default Dependencies" for details.</para> |
ae0a5fb1 | 706 | |
61ad59b1 LP |
707 | </listitem> |
708 | </varlistentry> | |
709 | ||
a931ad47 LP |
710 | <varlistentry> |
711 | <term><varname>Delegate=</varname></term> | |
712 | ||
713 | <listitem> | |
a9f01ad1 LP |
714 | <para>Turns on delegation of further resource control partitioning to processes of the unit. Units where this |
715 | is enabled may create and manage their own private subhierarchy of control groups below the control group of | |
716 | the unit itself. For unprivileged services (i.e. those using the <varname>User=</varname> setting) the unit's | |
717 | control group will be made accessible to the relevant user. When enabled the service manager will refrain | |
718 | from manipulating control groups or moving processes below the unit's control group, so that a clear concept | |
719 | of ownership is established: the control group tree above the unit's control group (i.e. towards the root | |
720 | control group) is owned and managed by the service manager of the host, while the control group tree below | |
721 | the unit's control group is owned and managed by the unit itself. Takes either a boolean argument or a list | |
722 | of control group controller names. If true, delegation is turned on, and all supported controllers are | |
723 | enabled for the unit, making them available to the unit's processes for management. If false, delegation is | |
724 | turned off entirely (and no additional controllers are enabled). If set to a list of controllers, delegation | |
725 | is turned on, and the specified controllers are enabled for the unit. Note that assigning the empty string | |
726 | will enable delegation, but not enable any additional controllers. Defaults to false.</para> | |
727 | ||
728 | <para>Note that controller delegation to less privileged code is only safe on the unified control group | |
729 | hierarchy. Accordingly, access to the specified controllers will not be granted to unprivileged services on | |
730 | the legacy hierarchy, even when requested.</para> | |
731 | ||
732 | <para>The following controller names may be specified: <option>cpu</option>, <option>cpuacct</option>, | |
733 | <option>io</option>, <option>blkio</option>, <option>memory</option>, <option>devices</option>, | |
734 | <option>pids</option>. Not all of these controllers are available on all kernels however, and some are | |
735 | specific to the unified hierarchy while others are specific to the legacy hierarchy. Also note that the | |
736 | kernel might support further controllers, which aren't covered here yet as delegation is either not supported | |
737 | at all for them or not defined cleanly.</para> | |
a931ad47 LP |
738 | </listitem> |
739 | </varlistentry> | |
740 | ||
d868475a ZJS |
741 | </variablelist> |
742 | </refsect1> | |
743 | ||
7d862ab8 TH |
744 | <refsect1> |
745 | <title>Deprecated Options</title> | |
746 | ||
747 | <para>The following options are deprecated. Use the indicated superseding options instead:</para> | |
748 | ||
749 | <variablelist class='unit-directives'> | |
750 | ||
751 | <varlistentry> | |
752 | <term><varname>CPUShares=<replaceable>weight</replaceable></varname></term> | |
753 | <term><varname>StartupCPUShares=<replaceable>weight</replaceable></varname></term> | |
754 | ||
755 | <listitem> | |
756 | <para>Assign the specified CPU time share weight to the processes executed. These options take an integer | |
757 | value and control the <literal>cpu.shares</literal> control group attribute. The allowed range is 2 to | |
758 | 262144. Defaults to 1024. For details about this control group attribute, see <ulink | |
759 | url="https://www.kernel.org/doc/Documentation/scheduler/sched-design-CFS.txt">sched-design-CFS.txt</ulink>. | |
760 | The available CPU time is split up among all units within one slice relative to their CPU time share | |
761 | weight.</para> | |
762 | ||
763 | <para>While <varname>StartupCPUShares=</varname> only applies to the startup phase of the system, | |
764 | <varname>CPUShares=</varname> applies to normal runtime of the system, and if the former is not set also to | |
765 | the startup phase. Using <varname>StartupCPUShares=</varname> allows prioritizing specific services at | |
766 | boot-up differently than during normal runtime.</para> | |
767 | ||
768 | <para>Implies <literal>CPUAccounting=true</literal>.</para> | |
769 | ||
770 | <para>These settings are deprecated. Use <varname>CPUWeight=</varname> and | |
771 | <varname>StartupCPUWeight=</varname> instead.</para> | |
772 | </listitem> | |
773 | </varlistentry> | |
774 | ||
775 | <varlistentry> | |
776 | <term><varname>MemoryLimit=<replaceable>bytes</replaceable></varname></term> | |
777 | ||
778 | <listitem> | |
779 | <para>Specify the limit on maximum memory usage of the executed processes. The limit specifies how much | |
780 | process and kernel memory can be used by tasks in this unit. Takes a memory size in bytes. If the value is | |
781 | suffixed with K, M, G or T, the specified memory size is parsed as Kilobytes, Megabytes, Gigabytes, or | |
782 | Terabytes (with the base 1024), respectively. Alternatively, a percentage value may be specified, which is | |
783 | taken relative to the installed physical memory on the system. If assigned the special value | |
784 | <literal>infinity</literal>, no memory limit is applied. This controls the | |
785 | <literal>memory.limit_in_bytes</literal> control group attribute. For details about this control group | |
786 | attribute, see <ulink | |
787 | url="https://www.kernel.org/doc/Documentation/cgroup-v1/memory.txt">memory.txt</ulink>.</para> | |
788 | ||
789 | <para>Implies <literal>MemoryAccounting=true</literal>.</para> | |
790 | ||
791 | <para>This setting is deprecated. Use <varname>MemoryMax=</varname> instead.</para> | |
792 | </listitem> | |
793 | </varlistentry> | |
794 | ||
795 | <varlistentry> | |
796 | <term><varname>BlockIOAccounting=</varname></term> | |
797 | ||
798 | <listitem> | |
799 | <para>Turn on Block I/O accounting for this unit, if the legacy control group hierarchy is used on the | |
800 | system. Takes a boolean argument. Note that turning on block I/O accounting for one unit will also implicitly | |
801 | turn it on for all units contained in the same slice and all for its parent slices and the units contained | |
802 | therein. The system default for this setting may be controlled with | |
803 | <varname>DefaultBlockIOAccounting=</varname> in | |
804 | <citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para> | |
805 | ||
806 | <para>This setting is deprecated. Use <varname>IOAccounting=</varname> instead.</para> | |
807 | </listitem> | |
808 | </varlistentry> | |
809 | ||
810 | <varlistentry> | |
811 | <term><varname>BlockIOWeight=<replaceable>weight</replaceable></varname></term> | |
812 | <term><varname>StartupBlockIOWeight=<replaceable>weight</replaceable></varname></term> | |
813 | ||
814 | <listitem><para>Set the default overall block I/O weight for the executed processes, if the legacy control | |
815 | group hierarchy is used on the system. Takes a single weight value (between 10 and 1000) to set the default | |
816 | block I/O weight. This controls the <literal>blkio.weight</literal> control group attribute, which defaults to | |
817 | 500. For details about this control group attribute, see <ulink | |
818 | url="https://www.kernel.org/doc/Documentation/cgroup-v1/blkio-controller.txt">blkio-controller.txt</ulink>. | |
819 | The available I/O bandwidth is split up among all units within one slice relative to their block I/O | |
820 | weight.</para> | |
821 | ||
822 | <para>While <varname>StartupBlockIOWeight=</varname> only | |
823 | applies to the startup phase of the system, | |
824 | <varname>BlockIOWeight=</varname> applies to the later runtime | |
825 | of the system, and if the former is not set also to the | |
826 | startup phase. This allows prioritizing specific services at | |
827 | boot-up differently than during runtime.</para> | |
828 | ||
829 | <para>Implies | |
830 | <literal>BlockIOAccounting=true</literal>.</para> | |
831 | ||
832 | <para>These settings are deprecated. Use <varname>IOWeight=</varname> and <varname>StartupIOWeight=</varname> | |
833 | instead.</para> | |
834 | ||
835 | </listitem> | |
836 | </varlistentry> | |
837 | ||
838 | <varlistentry> | |
839 | <term><varname>BlockIODeviceWeight=<replaceable>device</replaceable> <replaceable>weight</replaceable></varname></term> | |
840 | ||
841 | <listitem> | |
842 | <para>Set the per-device overall block I/O weight for the executed processes, if the legacy control group | |
843 | hierarchy is used on the system. Takes a space-separated pair of a file path and a weight value to specify | |
844 | the device specific weight value, between 10 and 1000. (Example: "/dev/sda 500"). The file path may be | |
845 | specified as path to a block device node or as any other file, in which case the backing block device of the | |
846 | file system of the file is determined. This controls the <literal>blkio.weight_device</literal> control group | |
847 | attribute, which defaults to 1000. Use this option multiple times to set weights for multiple devices. For | |
848 | details about this control group attribute, see <ulink | |
849 | url="https://www.kernel.org/doc/Documentation/cgroup-v1/blkio-controller.txt">blkio-controller.txt</ulink>.</para> | |
850 | ||
851 | <para>Implies | |
852 | <literal>BlockIOAccounting=true</literal>.</para> | |
853 | ||
854 | <para>This setting is deprecated. Use <varname>IODeviceWeight=</varname> instead.</para> | |
855 | </listitem> | |
856 | </varlistentry> | |
857 | ||
858 | <varlistentry> | |
859 | <term><varname>BlockIOReadBandwidth=<replaceable>device</replaceable> <replaceable>bytes</replaceable></varname></term> | |
860 | <term><varname>BlockIOWriteBandwidth=<replaceable>device</replaceable> <replaceable>bytes</replaceable></varname></term> | |
861 | ||
862 | <listitem> | |
863 | <para>Set the per-device overall block I/O bandwidth limit for the executed processes, if the legacy control | |
864 | group hierarchy is used on the system. Takes a space-separated pair of a file path and a bandwidth value (in | |
865 | bytes per second) to specify the device specific bandwidth. The file path may be a path to a block device | |
866 | node, or as any other file in which case the backing block device of the file system of the file is used. If | |
867 | the bandwidth is suffixed with K, M, G, or T, the specified bandwidth is parsed as Kilobytes, Megabytes, | |
868 | Gigabytes, or Terabytes, respectively, to the base of 1000. (Example: | |
869 | "/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0 5M"). This controls the | |
870 | <literal>blkio.throttle.read_bps_device</literal> and <literal>blkio.throttle.write_bps_device</literal> | |
871 | control group attributes. Use this option multiple times to set bandwidth limits for multiple devices. For | |
872 | details about these control group attributes, see <ulink | |
873 | url="https://www.kernel.org/doc/Documentation/cgroup-v1/blkio-controller.txt">blkio-controller.txt</ulink>. | |
874 | </para> | |
875 | ||
876 | <para>Implies | |
877 | <literal>BlockIOAccounting=true</literal>.</para> | |
878 | ||
879 | <para>These settings are deprecated. Use <varname>IOReadBandwidthMax=</varname> and | |
880 | <varname>IOWriteBandwidthMax=</varname> instead.</para> | |
881 | </listitem> | |
882 | </varlistentry> | |
883 | ||
884 | </variablelist> | |
885 | </refsect1> | |
886 | ||
d868475a ZJS |
887 | <refsect1> |
888 | <title>See Also</title> | |
889 | <para> | |
890 | <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>, | |
891 | <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>, | |
892 | <citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>, | |
893 | <citerefentry><refentrytitle>systemd.slice</refentrytitle><manvolnum>5</manvolnum></citerefentry>, | |
894 | <citerefentry><refentrytitle>systemd.scope</refentrytitle><manvolnum>5</manvolnum></citerefentry>, | |
895 | <citerefentry><refentrytitle>systemd.socket</refentrytitle><manvolnum>5</manvolnum></citerefentry>, | |
896 | <citerefentry><refentrytitle>systemd.mount</refentrytitle><manvolnum>5</manvolnum></citerefentry>, | |
897 | <citerefentry><refentrytitle>systemd.swap</refentrytitle><manvolnum>5</manvolnum></citerefentry>, | |
74b47bbd | 898 | <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>, |
d868475a | 899 | <citerefentry><refentrytitle>systemd.directives</refentrytitle><manvolnum>7</manvolnum></citerefentry>, |
61ad59b1 | 900 | <citerefentry><refentrytitle>systemd.special</refentrytitle><manvolnum>7</manvolnum></citerefentry>, |
d868475a | 901 | The documentation for control groups and specific controllers in the Linux kernel: |
c51fa947 MP |
902 | <ulink url="https://www.kernel.org/doc/Documentation/cgroup-v1/cgroups.txt">cgroups.txt</ulink>, |
903 | <ulink url="https://www.kernel.org/doc/Documentation/cgroup-v1/cpuacct.txt">cpuacct.txt</ulink>, | |
904 | <ulink url="https://www.kernel.org/doc/Documentation/cgroup-v1/memory.txt">memory.txt</ulink>, | |
905 | <ulink url="https://www.kernel.org/doc/Documentation/cgroup-v1/blkio-controller.txt">blkio-controller.txt</ulink>. | |
d868475a ZJS |
906 | </para> |
907 | </refsect1> | |
908 | </refentry> |