From: Kamalesh Babulal <kamalesh.babulal@oracle.com>
To: Xiu Jianfeng <xiujianfeng@huawei.com>,
tj@kernel.org, lizefan.x@bytedance.com, hannes@cmpxchg.org,
corbet@lwn.net, haitao.huang@linux.intel.com
Cc: cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 -next] cgroup/misc: Introduce misc.peak
Date: Wed, 3 Jul 2024 15:13:29 +0530 [thread overview]
Message-ID: <cb6bc4b9-bbf3-4d43-aeb8-8efdcbf94a9c@oracle.com> (raw)
In-Reply-To: <20240703003646.2762150-1-xiujianfeng@huawei.com>
On 7/3/24 6:06 AM, Xiu Jianfeng wrote:
> Introduce misc.peak to record the historical maximum usage of the
> resource, as in some scenarios the value of misc.max could be
> adjusted based on the peak usage of the resource.
>
[...]
> /**
> * misc_cg_capacity_show() - Show the total capacity of misc res on the host.
> * @sf: Interface file
> @@ -357,6 +394,10 @@ static struct cftype misc_cg_files[] = {
> .name = "current",
> .seq_show = misc_cg_current_show,
> },
> + {
> + .name = "peak",
> + .seq_show = misc_cg_peak_show,
> + },
> {
> .name = "capacity",
> .seq_show = misc_cg_capacity_show,
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?
--
Thanks,
Kamalesh
next prev parent reply other threads:[~2024-07-03 9:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 0:36 [PATCH v5 -next] cgroup/misc: Introduce misc.peak Xiu Jianfeng
2024-07-03 9:43 ` Kamalesh Babulal [this message]
2024-07-03 18:03 ` Tejun Heo
2024-07-04 5:54 ` Kamalesh Babulal
2024-07-03 18:09 ` Tejun Heo
2024-07-08 11:48 ` Haitao Huang
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=cb6bc4b9-bbf3-4d43-aeb8-8efdcbf94a9c@oracle.com \
--to=kamalesh.babulal@oracle.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=haitao.huang@linux.intel.com \
--cc=hannes@cmpxchg.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=tj@kernel.org \
--cc=xiujianfeng@huawei.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