[<prev] [next>] [day] [month] [year] [list]
Message-ID: <Y/jRibeqSlO1Z55I@dhcp22.suse.cz>
Date: Fri, 24 Feb 2023 16:02:33 +0100
From: Michal Hocko <mhocko@...e.com>
To: Matthew Chae <matthewc@...s.com>
Cc: Matthew Chae <Matthew.Chae@...s.com>,
Roman Gushchin <roman.gushchin@...ux.dev>,
Michal Koutný <mkoutny@...e.com>,
Johannes Weiner <hannes@...xchg.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 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
Powered by blists - more mailing lists