From: Michal Hocko <mhocko@suse.com>
To: Aaron Tomlin <atomlin@redhat.com>
Cc: linux-kernel@vger.kernel.org, hannes@cmpxchg.org,
vdavydov.dev@gmail.com, akpm@linux-foundation.org,
cgroups@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] memcg: add support to generate the total count of children from root
Date: Tue, 24 Nov 2020 12:26:12 +0100 [thread overview]
Message-ID: <20201124112612.GV27488@dhcp22.suse.cz> (raw)
In-Reply-To: <20201124105836.713371-1-atomlin@redhat.com>
On Tue 24-11-20 10:58:36, Aaron Tomlin wrote:
> Each memory-controlled cgroup is assigned a unique ID and the total
> number of memory cgroups is limited to MEM_CGROUP_ID_MAX.
>
> This patch provides the ability to determine the number of
> memory cgroups from the root memory cgroup, only.
> A value of 1 (i.e. self count) is returned if there are no children.
> For example, the number of memory cgroups can be established by
> reading the /sys/fs/cgroup/memory/memory.total_cnt file.
Could you add some explanation why is this information useful for
userspace? Who is going to use it and why a simple scripting on top of
cgroupfs is insufficient.
> Signed-off-by: Aaron Tomlin <atomlin@redhat.com>
> ---
> mm/memcontrol.c | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index 29459a6ce1c7..a4f7cb40e233 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -4535,6 +4535,19 @@ static int mem_cgroup_oom_control_write(struct cgroup_subsys_state *css,
> return 0;
> }
>
> +static int mem_cgroup_total_count_read(struct cgroup_subsys_state *css,
> + struct cftype *cft)
> +{
> + struct mem_cgroup *iter, *memcg = mem_cgroup_from_css(css);
> + int num = 0;
> +
> + for_each_mem_cgroup_tree(iter, memcg)
> + num++;
> +
> + /* Returns 1 (i.e. self count) if no children. */
> + return num;
> +}
> +
> #ifdef CONFIG_CGROUP_WRITEBACK
>
> #include <trace/events/writeback.h>
> @@ -5050,6 +5063,11 @@ static struct cftype mem_cgroup_legacy_files[] = {
> .write_u64 = mem_cgroup_oom_control_write,
> .private = MEMFILE_PRIVATE(_OOM_TYPE, OOM_CONTROL),
> },
> + {
> + .name = "total_cnt",
> + .flags = CFTYPE_ONLY_ON_ROOT,
> + .read_u64 = mem_cgroup_total_count_read,
> + },
> {
> .name = "pressure_level",
> },
> --
> 2.26.2
>
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2020-11-24 11:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 10:58 Aaron Tomlin
2020-11-24 11:26 ` Michal Hocko [this message]
2020-11-24 13:27 ` Aaron Tomlin
2020-11-24 13:36 ` Michal Hocko
2020-11-24 13:47 ` Aaron Tomlin
2020-11-26 11:02 ` Aaron Tomlin
2020-11-24 13:36 ` Aaron Tomlin
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=20201124112612.GV27488@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=atomlin@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vdavydov.dev@gmail.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