[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230223142053.ejpygn4asiks7uue@blackpad>
Date: Thu, 23 Feb 2023 15:20:53 +0100
From: Michal Koutný <mkoutny@...e.com>
To: Matthew Chae <matthew.chae@...s.com>
Cc: Johannes Weiner <hannes@...xchg.org>,
Michal Hocko <mhocko@...nel.org>,
Roman Gushchin <roman.gushchin@...ux.dev>,
Shakeel Butt <shakeelb@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>, kernel@...s.com,
christopher.wong@...s.com, Muchun Song <muchun.song@...ux.dev>,
cgroups@...r.kernel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm/memcontrol: add memory.peak in cgroup root
Hello Matthew.
On Tue, Feb 21, 2023 at 03:34:20PM +0100, Matthew Chae <matthew.chae@...s.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
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists