From: Shakeel Butt <shakeel.butt@linux.dev>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Michal Hocko" <mhocko@kernel.org>, "Tejun Heo" <tj@kernel.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Roman Gushchin" <roman.gushchin@linux.dev>,
"Muchun Song" <muchun.song@linux.dev>,
"Michal Koutný" <mkoutny@suse.com>,
linux-mm@kvack.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Meta kernel team" <kernel-team@meta.com>
Subject: Re: [PATCH] memcg: add hierarchical effective limits for v2
Date: Thu, 6 Feb 2025 14:24:57 -0800 [thread overview]
Message-ID: <6bs4tywynoay7q7uxgvwo5s2j2gk4osulsbdj2u4ujn55jcpne@qektqs6524xa> (raw)
In-Reply-To: <20250205222029.2979048-1-shakeel.butt@linux.dev>
Oops, I forgot to CC Andrew.
On Wed, Feb 05, 2025 at 02:20:29PM -0800, Shakeel Butt 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.
>
> Signed-off-by: Shakeel Butt <shakeel.butt@linux.dev>
> ---
> Documentation/admin-guide/cgroup-v2.rst | 24 +++++++++++++
> mm/memcontrol.c | 48 +++++++++++++++++++++++++
> 2 files changed, 72 insertions(+)
>
> diff --git a/Documentation/admin-guide/cgroup-v2.rst b/Documentation/admin-guide/cgroup-v2.rst
> index cb1b4e759b7e..175e9435ad5c 100644
> --- a/Documentation/admin-guide/cgroup-v2.rst
> +++ b/Documentation/admin-guide/cgroup-v2.rst
> @@ -1311,6 +1311,14 @@ PAGE_SIZE multiple when read back.
> Caller could retry them differently, return into userspace
> as -ENOMEM or silently ignore in cases like disk readahead.
>
> + memory.max.effective
> + A read-only single value file which exists on non-root cgroups.
> +
> + The effective limit of the cgroup i.e. the minimum memory.max
> + of all ancestors including itself. This is useful for environments
> + where cgroup namespace is being used and the application does not
> + have full view of the hierarchy.
> +
> memory.reclaim
> A write-only nested-keyed file which exists for all cgroups.
>
> @@ -1726,6 +1734,14 @@ The following nested keys are defined.
> Swap usage hard limit. If a cgroup's swap usage reaches this
> limit, anonymous memory of the cgroup will not be swapped out.
>
> + memory.swap.max.effective
> + A read-only single value file which exists on non-root cgroups.
> +
> + The effective limit of the cgroup i.e. the minimum memory.swap.max
> + of all ancestors including itself. This is useful for environments
> + where cgroup namespace is being used and the application does not
> + have full view of the hierarchy.
> +
> memory.swap.events
> A read-only flat-keyed file which exists on non-root cgroups.
> The following entries are defined. Unless specified
> @@ -1766,6 +1782,14 @@ The following nested keys are defined.
> limit, it will refuse to take any more stores before existing
> entries fault back in or are written out to disk.
>
> + memory.zswap.max.effective
> + A read-only single value file which exists on non-root cgroups.
> +
> + The effective limit of the cgroup i.e. the minimum memory.zswap.max
> + of all ancestors including itself. This is useful for environments
> + where cgroup namespace is being used and the application does not
> + have full view of the hierarchy.
> +
> memory.zswap.writeback
> A read-write single value file. The default value is "1".
> Note that this setting is hierarchical, i.e. the writeback would be
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index cae1c2e0cc71..8d21c1a44220 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -4161,6 +4161,17 @@ static int memory_max_show(struct seq_file *m, void *v)
> READ_ONCE(mem_cgroup_from_seq(m)->memory.max));
> }
>
> +static int memory_max_effective_show(struct seq_file *m, void *v)
> +{
> + unsigned long max = PAGE_COUNTER_MAX;
> + struct mem_cgroup *memcg = mem_cgroup_from_seq(m);
> +
> + for (; memcg; memcg = parent_mem_cgroup(memcg))
> + max = min(max, READ_ONCE(memcg->memory.max));
> +
> + return seq_puts_memcg_tunable(m, max);
> +}
> +
> static ssize_t memory_max_write(struct kernfs_open_file *of,
> char *buf, size_t nbytes, loff_t off)
> {
> @@ -4438,6 +4449,11 @@ static struct cftype memory_files[] = {
> .seq_show = memory_max_show,
> .write = memory_max_write,
> },
> + {
> + .name = "max.effective",
> + .flags = CFTYPE_NOT_ON_ROOT,
> + .seq_show = memory_max_effective_show,
> + },
> {
> .name = "events",
> .flags = CFTYPE_NOT_ON_ROOT,
> @@ -5117,6 +5133,17 @@ static int swap_max_show(struct seq_file *m, void *v)
> READ_ONCE(mem_cgroup_from_seq(m)->swap.max));
> }
>
> +static int swap_max_effective_show(struct seq_file *m, void *v)
> +{
> + unsigned long max = PAGE_COUNTER_MAX;
> + struct mem_cgroup *memcg = mem_cgroup_from_seq(m);
> +
> + for (; memcg; memcg = parent_mem_cgroup(memcg))
> + max = min(max, READ_ONCE(memcg->swap.max));
> +
> + return seq_puts_memcg_tunable(m, max);
> +}
> +
> static ssize_t swap_max_write(struct kernfs_open_file *of,
> char *buf, size_t nbytes, loff_t off)
> {
> @@ -5166,6 +5193,11 @@ static struct cftype swap_files[] = {
> .seq_show = swap_max_show,
> .write = swap_max_write,
> },
> + {
> + .name = "swap.max.effective",
> + .flags = CFTYPE_NOT_ON_ROOT,
> + .seq_show = swap_max_effective_show,
> + },
> {
> .name = "swap.peak",
> .flags = CFTYPE_NOT_ON_ROOT,
> @@ -5308,6 +5340,17 @@ static int zswap_max_show(struct seq_file *m, void *v)
> READ_ONCE(mem_cgroup_from_seq(m)->zswap_max));
> }
>
> +static int zswap_max_effective_show(struct seq_file *m, void *v)
> +{
> + unsigned long max = PAGE_COUNTER_MAX;
> + struct mem_cgroup *memcg = mem_cgroup_from_seq(m);
> +
> + for (; memcg; memcg = parent_mem_cgroup(memcg))
> + max = min(max, READ_ONCE(memcg->zswap_max));
> +
> + return seq_puts_memcg_tunable(m, max);
> +}
> +
> static ssize_t zswap_max_write(struct kernfs_open_file *of,
> char *buf, size_t nbytes, loff_t off)
> {
> @@ -5362,6 +5405,11 @@ static struct cftype zswap_files[] = {
> .seq_show = zswap_max_show,
> .write = zswap_max_write,
> },
> + {
> + .name = "zswap.max.effective",
> + .flags = CFTYPE_NOT_ON_ROOT,
> + .seq_show = zswap_max_effective_show,
> + },
> {
> .name = "zswap.writeback",
> .seq_show = zswap_writeback_show,
> --
> 2.43.5
>
prev parent reply other threads:[~2025-02-06 22:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 22:20 Shakeel Butt
2025-02-05 22:33 ` Balbir Singh
2025-02-06 15:57 ` Michal Koutný
2025-02-06 19:09 ` Shakeel Butt
2025-02-06 19:37 ` T.J. Mercier
2025-02-10 16:24 ` Michal Koutný
2025-02-10 18:34 ` Shakeel Butt
2025-02-10 22:52 ` Johannes Weiner
2025-02-11 4:55 ` Roman Gushchin
2025-02-12 1:08 ` Shakeel Butt
2025-02-17 17:57 ` Michal Koutný
2025-02-26 21:13 ` Shakeel Butt
2025-02-27 3:51 ` Johannes Weiner
2025-03-17 1:12 ` Andrew Morton
2025-03-17 18:06 ` Tejun Heo
2025-02-06 22:24 ` Shakeel Butt [this message]
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=6bs4tywynoay7q7uxgvwo5s2j2gk4osulsbdj2u4ujn55jcpne@qektqs6524xa \
--to=shakeel.butt@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mkoutny@suse.com \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=tj@kernel.org \
/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