From: Shakeel Butt <shakeelb@google.com>
To: David Rientjes <rientjes@google.com>
Cc: SeongJae Park <sjpark@amazon.com>,
Andrew Morton <akpm@linux-foundation.org>,
Yang Shi <shy828301@gmail.com>, Michal Hocko <mhocko@kernel.org>,
Yang Shi <yang.shi@linux.alibaba.com>,
Roman Gushchin <guro@fb.com>, Greg Thelen <gthelen@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Cgroups <cgroups@vger.kernel.org>, Linux MM <linux-mm@kvack.org>
Subject: Re: [patch] mm, memcg: provide an anon_reclaimable stat
Date: Thu, 16 Jul 2020 14:07:13 -0700 [thread overview]
Message-ID: <CALvZod6DbAUA-M9VXJW4RumeUD8qGf+BHM+9TUNeAr92JVkxsA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.23.453.2007161357490.3209847@chino.kir.corp.google.com>
On Thu, Jul 16, 2020 at 1:58 PM David Rientjes <rientjes@google.com> wrote:
>
> Userspace can lack insight into the amount of memory that can be reclaimed
> from a memcg based on values from memory.stat. Two specific examples:
>
> - Lazy freeable memory (MADV_FREE) that are clean anonymous pages on the
> inactive file LRU that can be quickly reclaimed under memory pressure
> but otherwise shows up as mapped anon in memory.stat, and
>
> - Memory on deferred split queues (thp) that are compound pages that can
> be split and uncharged from the memcg under memory pressure, but
> otherwise shows up as charged anon LRU memory in memory.stat.
>
> Both of this anonymous usage is also charged to memory.current.
>
> Userspace can currently derive this information but it depends on kernel
> implementation details for how this memory is handled for the purposes of
> reclaim (anon on inactive file LRU or unmapped anon on the LRU).
>
> For the purposes of writing portable userspace code that does not need to
> have insight into the kernel implementation for reclaimable memory, this
> exports a stat that reveals the amount of anonymous memory that can be
> reclaimed and uncharged from the memcg to start new applications.
>
> As the kernel implementation evolves for memory that can be reclaimed
> under memory pressure, this stat can be kept consistent.
>
> Signed-off-by: David Rientjes <rientjes@google.com>
> ---
> Documentation/admin-guide/cgroup-v2.rst | 6 +++++
> mm/memcontrol.c | 31 +++++++++++++++++++++++++
> 2 files changed, 37 insertions(+)
>
> diff --git a/Documentation/admin-guide/cgroup-v2.rst b/Documentation/admin-guide/cgroup-v2.rst
> --- a/Documentation/admin-guide/cgroup-v2.rst
> +++ b/Documentation/admin-guide/cgroup-v2.rst
> @@ -1296,6 +1296,12 @@ PAGE_SIZE multiple when read back.
> Amount of memory used in anonymous mappings backed by
> transparent hugepages
>
> + anon_reclaimable
> + The amount of charged anonymous memory that can be reclaimed
> + under memory pressure without swap. This currently includes
> + lazy freeable memory (MADV_FREE) and compound pages that can be
> + split and uncharged.
> +
> inactive_anon, active_anon, inactive_file, active_file, unevictable
> Amount of memory, swap-backed and filesystem-backed,
> on the internal memory management lists used by the
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -1350,6 +1350,32 @@ static bool mem_cgroup_wait_acct_move(struct mem_cgroup *memcg)
> return false;
> }
>
> +/*
> + * Returns the amount of anon memory that is charged to the memcg that is
> + * reclaimable under memory pressure without swap, in pages.
> + */
> +static unsigned long memcg_anon_reclaimable(struct mem_cgroup *memcg)
> +{
> + long deferred, lazyfree;
> +
> + /*
> + * Deferred pages are charged anonymous pages that are on the LRU but
> + * are unmapped. These compound pages are split under memory pressure.
> + */
> + deferred = max_t(long, memcg_page_state(memcg, NR_ACTIVE_ANON) +
> + memcg_page_state(memcg, NR_INACTIVE_ANON) -
> + memcg_page_state(memcg, NR_ANON_MAPPED), 0);
Please note that the NR_ANON_MAPPED does not include tmpfs memory but
NR_[IN]ACTIVE_ANON does include the tmpfs.
> + /*
> + * Lazyfree pages are charged clean anonymous pages that are on the file
> + * LRU and can be reclaimed under memory pressure.
> + */
> + lazyfree = max_t(long, memcg_page_state(memcg, NR_ACTIVE_FILE) +
> + memcg_page_state(memcg, NR_INACTIVE_FILE) -
> + memcg_page_state(memcg, NR_FILE_PAGES), 0);
Similarly NR_FILE_PAGES includes tmpfs memory but NR_[IN]ACTIVE_FILE does not.
next prev parent reply other threads:[~2020-07-16 21:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 3:18 [patch] mm, memcg: provide a stat to describe reclaimable memory David Rientjes
2020-07-15 7:00 ` David Rientjes
2020-07-15 7:15 ` SeongJae Park
2020-07-15 17:33 ` David Rientjes
2020-07-16 20:58 ` [patch] mm, memcg: provide an anon_reclaimable stat David Rientjes
2020-07-16 21:07 ` Shakeel Butt [this message]
2020-07-16 21:28 ` David Rientjes
2020-07-17 1:37 ` Shakeel Butt
2020-07-17 8:34 ` Michal Hocko
2020-07-17 14:39 ` Johannes Weiner
2020-07-15 13:10 ` [patch] mm, memcg: provide a stat to describe reclaimable memory Chris Down
[not found] ` <alpine.DEB.2.23.453.2007151046320.2788464@chino.kir.corp.google.com>
2020-07-17 12:17 ` Chris Down
2020-07-17 19:37 ` David Rientjes
2020-07-20 7:37 ` Michal Hocko
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=CALvZod6DbAUA-M9VXJW4RumeUD8qGf+BHM+9TUNeAr92JVkxsA@mail.gmail.com \
--to=shakeelb@google.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=gthelen@google.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=rientjes@google.com \
--cc=shy828301@gmail.com \
--cc=sjpark@amazon.com \
--cc=vdavydov.dev@gmail.com \
--cc=yang.shi@linux.alibaba.com \
/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