On Wed, May 11, 2022 at 8:18 AM Roman Gushchin <roman.gushchin@xxxxxxxxx> wrote: > > On Fri, May 06, 2022 at 10:09:16PM -0700, Ganesan Rajagopal wrote: > > We run a lot of automated tests when building our software and run into > > OOM scenarios when the tests run unbounded. v1 memcg exports > > memcg->watermark as "memory.max_usage_in_bytes" in sysfs. We use this > > metric to heuristically limit the number of tests that can run in > > parallel based on per test historical data. > > > > This metric is currently not exported for v2 memcg and there is no > > other easy way of getting this information. getrusage() syscall returns > > "ru_maxrss" which can be used as an approximation but that's the max > > RSS of a single child process across all children instead of the > > aggregated max for all child processes. The only work around is to > > periodically poll "memory.current" but that's not practical for > > short-lived one-off cgroups. > > > > Hence, expose memcg->watermark as "memory.peak" for v2 memcg. > > > > Signed-off-by: Ganesan Rajagopal <rganesan@xxxxxxxxxx> > > Acked-by: Roman Gushchin <roman.gushchin@xxxxxxxxx> > > I've been asked a couple of times about this feature, so I think it's indeed > useful. > > Thank you for adding it! You're welcome and thank you for the Ack. Thank you, Shakeel and Johannes for the review and Ack. The patch has been picked up for mm-unstable. Ganesan
