Lines Matching refs:this
16 concepts and interfaces involved with this.
21 comprehensive up-to-date information about all this, particular in light of the
39 wiki documentation into this very document, too.)
47 1. The **no-processes-in-inner-nodes** rule: this means that it's not permitted
52 exceptions to this rule, though. E.g. the root cgroup is special and allows
56 2. The **single-writer** rule: this means that each cgroup only has a single
63 These two rules have various effects. For example, one corollary of this is: if
70 violated. On cgroup v1 this rule didn't exist, and hence isn't enforced, even
72 either cgroup v1 nor cgroup v2 (this is UNIX after all, in the general case
80 kernel features in this area are only added to cgroup v2, and not cgroup v1
90 1. **Unified** — this is the simplest mode, and exposes a pure cgroup v2
91 logic. In this mode `/sys/fs/cgroup` is the only mounted cgroup API file system
94 2. **Legacy** — this is the traditional cgroup v1 mode. In this mode the
99 3. **Hybrid** — this is a hybrid between the unified and legacy mode. It's set
102 this mode the unified hierarchy won't have controllers attached, the
105 functionality and not about resource management.) In this mode compatibility
107 too. This mode is a stopgap. Don't bother with this too much unless you have
110 To say this clearly, legacy and hybrid modes have no future. If you develop
121 conceptually very close to the unified hierarchy. In particular this allows us
154 difference: the processes the units of this type encapsulate are forked off
162 3. �� The `.slice` unit type. Units of this type do not directly contain any
163 processes. Units of this type are the inner nodes of part of the cgroup tree
189 placed. `systemd-nspawn` makes use of this by default, and you're very welcome
238 specifically. Note that this only encodes a request. Depending on various
248 to them. If we'd allow delegation on slice units then this would mean that
260 was delegated to them. Note that this is only supported on kernels 5.6 and
281 this is a requirement of threaded cgroups: either a cgroup and all its siblings
292 1. �� The *integration-is-good* option. For this, you register each container
295 directly, but then tells systemd about it. In this mode the administrator
303 systemd via D-Bus. In this case systemd will just manage the unit for you
308 operations as in a. The main benefit of this: this way you let the system
309 know that what you are registering is a container, and this opens up
319 interest in integration with the rest of the system, then this is a valid
320 option. For this all you have to do is turn on `Delegate=` for your main
327 3. �� The *i-like-continents* option. In this option you'd leave your manager
331 `Delegate=` turned on, and it would contain the PID of this process; all
332 your managed processes subsequently created should also be moved into this
356 added to the kernel. However, regarding cgroup v1: at this point we will not
364 Effectively this means that all those mentioned cgroup v1 controllers are up
387 as necessary (as suggested above). However, on cgroup v2 this is different:
431 turn fork off the payload processes of the container. In this case don't
449 attribute name with an underscore. You might want to do the same, but this
488 this for you. (Specifically: each Unit object has a `ControlGroup` property