picnoir
/
Systemd
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

docs: clarify controller mount logic in hybrid cgroups mode 

Fixes: #10107
This commit is contained in:
Lennart Poettering 2018-09-24 19:01:37 +02:00 committed by Zbigniew Jędrzejewski-Szmek
parent 044c2c7a2b
commit 9afd574039
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/CGROUP_DELEGATION.md
View File

@ -91,10 +91,14 @@ hierarchy for managing purposes as `/sys/fs/cgroup/systemd/`.
3. **Hybrid** — this is a hybrid between the unified and legacy mode. It's set
up mostly like legacy, except that there's also an additional hierarchy
`/sys/fs/cgroup/unified/` that contains the cgroupsv2 hierarchy. In this mode
compatibility with cgroupsv1 is retained while some cgroupsv2 features are
available too. This mode is a stopgap. Don't bother with this too much unless
you have too much free time.
`/sys/fs/cgroup/unified/` that contains the cgroupsv2 hierarchy. (Note that in
this mode the unified hierarchy won't have controllers attached, the
controllers are all mounted as separate hierarchies as in legacy mode,
i.e. `/sys/fs/cgroup/unified/` is purely and exclusively about core cgroupsv2
functionality and not about resource management.) In this mode compatibility
with cgroupsv1 is retained while some cgroupsv2 features are available
too. This mode is a stopgap. Don't bother with this too much unless you have
too much free time.
To say this clearly, legacy and hybrid modes have no future. If you develop
software today and don't focus on the unified mode, then you are writing