From: Michal Hocko <mhocko@suse.com>
To: Christopher Wong <Christopher.Wong@axis.com>
Cc: Matthew Chae <Matthew.Chae@axis.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Shakeel Butt <shakeelb@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
kernel <kernel@axis.com>, Muchun Song <muchun.song@linux.dev>,
"cgroups@vger.kernel.org" <cgroups@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Sv: [PATCH] mm/memcontrol: add memory.peak in cgroup root
Date: Tue, 21 Feb 2023 17:16:55 +0100 [thread overview]
Message-ID: <Y/TudzUxEDwn6MHX@dhcp22.suse.cz> (raw)
In-Reply-To: <DB4PR02MB93344BAA949FA7E25E298C90FEA59@DB4PR02MB9334.eurprd02.prod.outlook.com>
On Tue 21-02-23 16:13:14, Christopher Wong wrote:
> Hi Michal,
>
> Thanks for the quick response! I think we are just trying to
> get the same value that was available for us in cgroup v1
> memory.max_usage_in_bytes. I guess this value also is incomplete for
> representing the system memory usage.
Correct.
> Is it due the incompleteness that the memory.peak has been left out in
> the root of cgroup v2?
I think so but I do not remember 100%. You might want to look into email
archives.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2023-02-21 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 14:34 Matthew Chae
2023-02-21 15:07 ` Michal Hocko
2023-02-21 16:13 ` Sv: " Christopher Wong
2023-02-21 16:16 ` Michal Hocko [this message]
2023-02-23 14:20 ` Michal Koutný
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=Y/TudzUxEDwn6MHX@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=Christopher.Wong@axis.com \
--cc=Matthew.Chae@axis.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeelb@google.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