From: Waiman Long <longman@redhat.com>
To: "Jan Kratochvil (Azul)" <jkratochvil@azul.com>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Michal Koutny <mkoutny@suse.com>
Subject: Re: [PATCH v3] cgroup2: New memory.max.effective like cgroup1 hierarchical_memory_limit
Date: Tue, 13 Feb 2024 14:08:46 -0500 [thread overview]
Message-ID: <e3a7daa9-d690-4ef2-8f6a-0641a14a6cb9@redhat.com> (raw)
In-Reply-To: <ZctiM5RintD_D0Lt@host1.jankratochvil.net>
On 2/13/24 07:36, Jan Kratochvil (Azul) wrote:
> Hello,
>
> cgroup1 (by function memcg1_stat_format) 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. Based on Michal Koutny's idea this
> patch now implements "memory.max.effective" and "memory.swap.max.effective"
> files similar to existing "cpuset.cpus.effective".
>
>
> Jan Kratochvil
>
>
> v3:
> memory.stat fields -> *.max.effective separate files suggested by Michal Koutny
> v2:
> hierarchical_memsw_limit -> hierarchical_swap_limit fix found by Waiman Long
> v1:
> hierarchical_memory_limit && hierarchical_memsw_limit in memory.stat
>
>
> Signed-off-by: Jan Kratochvil (Azul) <jkratochvil@azul.com>
The code changes look good to me. However, your commit log isn't of the
right format. We don't start the commit log with "Hello". See
https://www.kernel.org/doc/Documentation/process/submitting-patches.rst
You can also do a "git log" of a linux git tree and see how other people
write their commit logs.
Cheers,
Longman
>
> mm/memcontrol.c | 36 ++++++++++++++++++++++++++++++++++++
> 1 file changed, 36 insertions(+)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index 1ed40f9d3..8c4cb5f60 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -6845,6 +6845,19 @@ static ssize_t memory_max_write(struct kernfs_open_file *of,
> return nbytes;
> }
>
> +static int memory_max_effective_show(struct seq_file *m, void *v)
> +{
> + unsigned long memory;
> + struct mem_cgroup *mi;
> +
> + /* Hierarchical information */
> + memory = PAGE_COUNTER_MAX;
> + for (mi = mem_cgroup_from_seq(m); mi; mi = parent_mem_cgroup(mi))
> + memory = min(memory, READ_ONCE(mi->memory.max));
> +
> + return seq_puts_memcg_tunable(m, memory);
> +}
> +
> /*
> * Note: don't forget to update the 'samples/cgroup/memcg_event_listener'
> * if any new events become available.
> @@ -7038,6 +7051,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,
> @@ -8040,6 +8058,19 @@ static ssize_t swap_max_write(struct kernfs_open_file *of,
> return nbytes;
> }
>
> +static int swap_max_effective_show(struct seq_file *m, void *v)
> +{
> + unsigned long swap;
> + struct mem_cgroup *mi;
> +
> + /* Hierarchical information */
> + swap = PAGE_COUNTER_MAX;
> + for (mi = mem_cgroup_from_seq(m); mi; mi = parent_mem_cgroup(mi))
> + swap = min(swap, READ_ONCE(mi->swap.max));
> +
> + return seq_puts_memcg_tunable(m, swap);
> +}
> +
> static int swap_events_show(struct seq_file *m, void *v)
> {
> struct mem_cgroup *memcg = mem_cgroup_from_seq(m);
> @@ -8072,6 +8103,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,
>
prev parent reply other threads:[~2024-02-13 19:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 12:36 [PATCH v3] cgroup2: New memory.max.effective like cgroup1 hierarchical_memory_limit Jan Kratochvil (Azul)
2024-02-13 19:08 ` Waiman Long [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=e3a7daa9-d690-4ef2-8f6a-0641a14a6cb9@redhat.com \
--to=longman@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=jkratochvil@azul.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mkoutny@suse.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).