On Fri, 07 Jun 2024 02:15:00 +0800, Roman Gushchin wrote: > If the goal is to detect how much memory would it be possible to allocate, > I'm not sure that knowing all memory.max limits upper in the hierarchy > really buys anything without knowing actual usages and a potential > for memory reclaim across the entire tree. > > E.g.: > > A (max = 100G) > | \ > B C > > C's effective max will come out as 100G, but if B.anon_usage = 100G and > there is no swap, the actual number is 0. Yes, it would be better to subtract the used memory from ancestor (and thus even current) cgroups. The original use case of this feature is for cloud nodes running a single Java JVM where the sibling cgroups are not an issue. Jan Kratochvil
