[<prev] [next>] [day] [month] [year] [list]
Message-ID: <Y/eizTVo8LM70flh@P9FQF9L96D.corp.robot.car>
Date: Thu, 23 Feb 2023 09:30:53 -0800
From: Roman Gushchin <roman.gushchin@...ux.dev>
To: Matthew Chae <Matthew.Chae@...s.com>
Cc: Michal Koutný <mkoutny@...e.com>,
Johannes Weiner <hannes@...xchg.org>,
Michal Hocko <mhocko@...nel.org>,
Shakeel Butt <shakeelb@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
kernel <kernel@...s.com>,
Christopher Wong <Christopher.Wong@...s.com>,
Muchun Song <muchun.song@...ux.dev>,
"cgroups@...r.kernel.org" <cgroups@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mm/memcontrol: add memory.peak in cgroup root
On Thu, Feb 23, 2023 at 04:22:33PM +0000, Matthew Chae wrote:
> Hi Michal,
>
> First off, thank you for sharing your opinion.
> I'd like to monitor the peak memory usage recorded of overall system or at least cgroup accounted memory through memory.peak.
> But it looks like this is not relevant to what I wanted.
> It might be good to have some proper way for checking the system's peak memory usage recorded.
I guess you might want to do the opposite: instead of tracking the peak usage,
you can record the bottom of available free memory.
Thanks!
Powered by blists - more mailing lists