From: Waiman Long <longman@redhat.com>
To: "Jan Kratochvil (Azul)" <jkratochvil@azul.com>, cgroups@vger.kernel.org
Subject: Re: [PATCH] Port hierarchical_mem{ory,sw}_limit cgroup1->cgroup2
Date: Fri, 9 Feb 2024 10:51:54 -0500 [thread overview]
Message-ID: <284aefe1-fe85-48e9-b0f1-25e28be77198@redhat.com> (raw)
In-Reply-To: <ZcY7NmjkJMhGz8fP@host1.jankratochvil.net>
On 2/9/24 09:48, Jan Kratochvil (Azul) wrote:
> Hello,
>
> cgroup1 (by function memcg1_stat_format) already contains two lines
> hierarchical_memory_limit %llu
> hierarchical_memsw_limit %llu
>
> which are useful for userland to easily and performance-wise find out the
> effective cgroup limits being applied. Otherwise userland has to
> open+read+close the file "memory.max" and/or "memory.swap.max" in multiple
> parent directories of a nested cgroup.
>
> For cgroup1 it was implemented by:
> memcg: show real limit under hierarchy mode
> https://github.com/torvalds/linux/commit/fee7b548e6f2bd4bfd03a1a45d3afd593de7d5e9
> Date: Wed Jan 7 18:08:26 2009 -0800
>
> But for cgroup2 it has been missing so far, this is just a copy-paste of the
> cgroup1 code. I have added it to the end of "memory.stat" to prevent possible
> compatibility problems with existing code parsing that file.
>
>
> Jan Kratochvil
>
>
> Signed-off-by: Jan Kratochvil (Azul) <jkratochvil@azul.com>
>
> mm/memcontrol.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index 46d8d0211..39f2a4a06 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -1636,6 +1636,8 @@ static inline unsigned long memcg_page_state_local_output(
> static void memcg_stat_format(struct mem_cgroup *memcg, struct seq_buf *s)
> {
> int i;
> + unsigned long memory, memsw;
> + struct mem_cgroup *mi;
>
> /*
> * Provide statistics on the state of the memory subsystem as
> @@ -1682,6 +1684,17 @@ static void memcg_stat_format(struct mem_cgroup *memcg, struct seq_buf *s)
> memcg_events(memcg, memcg_vm_event_stat[i]));
> }
>
> + /* Hierarchical information */
> + memory = memsw = PAGE_COUNTER_MAX;
> + for (mi = memcg; mi; mi = parent_mem_cgroup(mi)) {
> + memory = min(memory, READ_ONCE(mi->memory.max));
> + memsw = min(memsw, READ_ONCE(mi->memsw.max));
> + }
> + seq_buf_printf(s, "hierarchical_memory_limit %llu\n",
> + (u64)memory * PAGE_SIZE);
> + seq_buf_printf(s, "hierarchical_memsw_limit %llu\n",
> + (u64)memsw * PAGE_SIZE);
> +
> /* The above should easily fit into one page */
> WARN_ON_ONCE(seq_buf_has_overflowed(s));
> }
I don't think we use mi->memsw in cgroup v2, only memory and swap should
be used.
Cheers,
Longman
>
next prev parent reply other threads:[~2024-02-09 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 14:48 [PATCH] Port hierarchical_mem{ory,sw}_limit cgroup1->cgroup2 Jan Kratochvil (Azul)
2024-02-09 15:51 ` Waiman Long [this message]
2024-02-11 12:49 ` [PATCH v2] Port hierarchical_{memory,swap}_limit cgroup1->cgroup2 Jan Kratochvil (Azul)
2024-02-11 18:01 ` Waiman Long
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=284aefe1-fe85-48e9-b0f1-25e28be77198@redhat.com \
--to=longman@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=jkratochvil@azul.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