[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <562ee18a-d433-4975-9737-a88ac6006916@oracle.com>
Date: Thu, 4 Jul 2024 11:24:58 +0530
From: Kamalesh Babulal <kamalesh.babulal@...cle.com>
To: Tejun Heo <tj@...nel.org>
Cc: Xiu Jianfeng <xiujianfeng@...wei.com>, lizefan.x@...edance.com,
hannes@...xchg.org, corbet@....net, haitao.huang@...ux.intel.com,
cgroups@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 -next] cgroup/misc: Introduce misc.peak
On 7/3/24 11:33 PM, Tejun Heo wrote:
> On Wed, Jul 03, 2024 at 03:13:29PM +0530, Kamalesh Babulal wrote:
> ...
>> The patch looks good to me after the atomic conversion. Sorry for bringing up
>> this question so late into the discussion. Given that misc.max is available
>> only for non-root cgroups, does it make sense for misc.peak too, available
>> for non-root cgroups only?
>
> It's more tied to the usage - misc.current. For memcg, memory.current is
> only on non-root cgroups, so is peak. For misc, as misc.current exists for
> the root cgroup, it makes sense for .peak to be there too.
>
Thank you so much for explaining in the context of misc controller.
--
Thanks,
Kamalesh
Powered by blists - more mailing lists