diff options
| author | Michal Koutný <mkoutny@suse.com> | 2025-11-14 19:21:26 +0100 |
|---|---|---|
| committer | Tejun Heo <tj@kernel.org> | 2025-11-14 11:21:05 -1000 |
| commit | 3755c11679d4f826e35d7a565ff366b8f64684c1 (patch) | |
| tree | 6fae2d93edc2f92d773a3cb303e873472a50c7ad | |
| parent | e27179958ce76b182ea38718113cdff1d2bb7d10 (diff) | |
docs: cgroup: Note about sibling relative reclaim protection
Signed-off-by: Michal Koutný <mkoutny@suse.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
| -rw-r--r-- | Documentation/admin-guide/cgroup-v2.rst | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/Documentation/admin-guide/cgroup-v2.rst b/Documentation/admin-guide/cgroup-v2.rst index 97a9f8a046c5..e0a659474fa4 100644 --- a/Documentation/admin-guide/cgroup-v2.rst +++ b/Documentation/admin-guide/cgroup-v2.rst @@ -1952,6 +1952,10 @@ When the reclaim targets ancestors of A, the effective protection of B is capped by the protection value configured for A (and any other intermediate ancestors between A and the target). +To express indifference about relative sibling protection, it is suggested to +use memory_recursiveprot. Configuring all descendants of a parent with finite +protection to "max" works but it may unnecessarily skew memory.events:low +field. Memory Ownership ~~~~~~~~~~~~~~~~ |