From: "Michal Koutný" <mkoutny@suse.com>
To: Matthew Chae <matthew.chae@axis.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Shakeel Butt <shakeelb@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
kernel@axis.com, christopher.wong@axis.com,
Muchun Song <muchun.song@linux.dev>,
cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/memcontrol: add memory.peak in cgroup root
Date: Thu, 23 Feb 2023 15:20:53 +0100 [thread overview]
Message-ID: <20230223142053.ejpygn4asiks7uue@blackpad> (raw)
In-Reply-To: <20230221143421.10385-1-matthew.chae@axis.com>
[-- Attachment #1: Type: text/plain, Size: 611 bytes --]
Hello Matthew.
On Tue, Feb 21, 2023 at 03:34:20PM +0100, Matthew Chae <matthew.chae@axis.com> wrote:
> The kernel currently doesn't provide any method to show the overall
> system's peak memory usage recorded. Instead, only each slice's peak
> memory usage recorded except for cgroup root is shown through each
> memory.peak.
The memory.peak value is useful as a calibration insight when you want to
configure memcg limit.
But there is no global (memcg) limit on memory. So what would be this
(not clearly) defined value good for? Or better then userspace sampling
of chosen available metric?
Thanks,
Michal
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-02-23 14:21 UTC|newest]
Thread overview: 13+ 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
2023-02-23 14:20 ` Michal Koutný [this message]
2023-02-23 16:22 Matthew Chae
2023-02-23 17:30 ` Roman Gushchin
2023-02-23 19:00 ` Matthew Chae
2023-02-23 22:00 ` Roman Gushchin
2023-02-24 8:23 ` Michal Hocko
2023-02-24 14:18 ` Matthew Chae
2023-02-24 15:02 ` Michal Hocko
2023-02-24 15:45 ` Matthew Chae
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=20230223142053.ejpygn4asiks7uue@blackpad \
--to=mkoutny@suse.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=christopher.wong@axis.com \
--cc=hannes@cmpxchg.org \
--cc=kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.chae@axis.com \
--cc=mhocko@kernel.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