From: Shakeel Butt <shakeelb@google.com>
To: Ganesan Rajagopal <rganesan@arista.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Cgroups <cgroups@vger.kernel.org>, Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH v2] mm/memcontrol: Export memcg->watermark via sysfs for v2 memcg
Date: Sat, 7 May 2022 08:33:46 -0700 [thread overview]
Message-ID: <CALvZod6upThQzqDGs1DCG4GuSf=rhfOncMU5=_eEoX8HH5Ri_w@mail.gmail.com> (raw)
In-Reply-To: <20220507050916.GA13577@us192.sjc.aristanetworks.com>
On Fri, May 6, 2022 at 10:09 PM Ganesan Rajagopal <rganesan@arista.com> 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@arista.com>
Acked-by: Shakeel Butt <shakeelb@google.com>
next prev parent reply other threads:[~2022-05-07 15:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 5:09 Ganesan Rajagopal
2022-05-07 15:33 ` Shakeel Butt [this message]
2022-05-09 13:44 ` Johannes Weiner
2022-05-11 2:48 ` Roman Gushchin
2022-05-11 3:47 ` Ganesan Rajagopal
2022-05-11 7:13 ` Michal Hocko
2022-05-11 7:22 ` Ganesan Rajagopal
2022-05-11 17:49 ` Michal Koutný
2022-05-12 2:48 ` Ganesan Rajagopal
2022-05-12 9:11 ` Michal Koutný
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALvZod6upThQzqDGs1DCG4GuSf=rhfOncMU5=_eEoX8HH5Ri_w@mail.gmail.com' \
--to=shakeelb@google.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=rganesan@arista.com \
--cc=roman.gushchin@linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox