From: Michal Hocko <mhocko@suse.com>
To: Matthew Chae <matthewc@axis.com>
Cc: "Matthew Chae" <Matthew.Chae@axis.com>,
"Roman Gushchin" <roman.gushchin@linux.dev>,
"Michal Koutný" <mkoutny@suse.com>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Shakeel Butt" <shakeelb@google.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
kernel <kernel@axis.com>,
"Christopher Wong" <Christopher.Wong@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: [PATCH] mm/memcontrol: add memory.peak in cgroup root
Date: Fri, 24 Feb 2023 16:02:33 +0100 [thread overview]
Message-ID: <Y/jRibeqSlO1Z55I@dhcp22.suse.cz> (raw)
In-Reply-To: <df9cc4e1-befc-af10-c353-733bec54baf1@axis.com>
On Fri 24-02-23 15:18:49, Matthew Chae wrote:
> Hi Michal
>
> Thank you for helping me gain full insight.
> It looks like there is no proper way to get the peak memory usage recorded
> without adding any overhead to the system and for all users. But I fully
> understand what you kindly explained. Basically, having low memory left
> doesn't mean a bad situation for the system, So checking the peak memory
> doesn't mean a lot and is not necessary.
You might find https://www.pdl.cmu.edu/ftp/NVM/tmo_asplos22.pdf
interesting and helpful
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2023-02-24 15:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2023-02-24 15:45 ` Matthew Chae
-- strict thread matches above, loose matches on Subject: below --
2023-02-21 14:34 Matthew Chae
2023-02-21 15:07 ` Michal Hocko
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/jRibeqSlO1Z55I@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=matthewc@axis.com \
--cc=mkoutny@suse.com \
--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