On Mon, Mar 17, 2025 at 08:36:36PM -0700, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > Memcg-v1 exposes hierarchical_[memory|memsw]_limit counters in its > memory.stat file which applications can use to get their effective limit > which is the minimum of limits of itself and all of its ancestors. This > is pretty useful in environments where cgroup namespace is used and the > application does not have access to the full view of the cgroup hierarchy. > Let's expose effective limits for memcg v2 as well. I understand the specific use case behind memory.max.effective (app's nested allocator can size its area based on that). That one can be a good starter. cgroup v2 has decoupled swap accounting though (in contrast to memsw), so I'm wondering what is memory.[z]swap.max.effective useful for the application? Is it expected that it'd adapt its behavior based on those values? > Link: https://lkml.kernel.org/r/20250205222029.2979048-1-shakeel.butt@xxxxxxxxx +Link: https://lore.kernel.org/all/20240606152232.20253-1-mkoutny@xxxxxxxx/ Michal
Attachment:
signature.asc
Description: PGP signature
