From: Chuyi Zhou <zhouchuyi@bytedance.com>
To: "Michal Koutný" <mkoutny@suse.com>
Cc: tj@kernel.org, hannes@cmpxchg.org, surenb@google.com,
peterz@infradead.org, chengming.zhou@linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] psi: Inherit parent cgroup psi enable state
Date: Tue, 30 Jul 2024 14:06:07 +0800 [thread overview]
Message-ID: <85bca797-6ddd-4541-ade5-a75864870472@bytedance.com> (raw)
In-Reply-To: <dxwvcccihuuxddycohyi5dj66o42rjekmkgxc7pzs344kvwuhd@3x6e5prw3xld>
Hello Michal,
在 2024/7/29 19:37, Michal Koutný 写道:
> Hello Chuyi.
>
> On Mon, Jul 29, 2024 at 11:41:00AM GMT, Chuyi Zhou <zhouchuyi@bytedance.com> wrote:
>> This patch tries to solve this issue. When a child cgroup is created, it
>> would inherit the psi enabled state of the parent in group_init().
>> Once the enable state is found to be false in the css_populate_dir(), the
>> {cpu, io, memory}.pressure files will be hidden using cgroup_file_show().
>
> I'd consider such an inheritance cgroupv1-ism. Notably,
> mmemory.swappiness also had inheritance and it caused some headaches
> because of its susceptibility to races (cgroup creation vs parent
> configuration).
Agree.
>
> What about adding an option (mount option?) to determine the default of
> per-cgroup pressure accounting?
> (Based on reading about your use case in other mail.) With that you
> could only enable it for the "online" groups of interest.
>
Yes. We can add a another mount option to disable the default PSI
accounting and enable the pod we interest.
Thanks.
prev parent reply other threads:[~2024-07-30 6:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 3:41 Chuyi Zhou
2024-07-29 4:45 ` K Prateek Nayak
2024-07-29 6:31 ` Chuyi Zhou
2024-07-29 7:48 ` K Prateek Nayak
2024-07-29 11:37 ` Michal Koutný
2024-07-30 6:06 ` Chuyi Zhou [this message]
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=85bca797-6ddd-4541-ade5-a75864870472@bytedance.com \
--to=zhouchuyi@bytedance.com \
--cc=chengming.zhou@linux.dev \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkoutny@suse.com \
--cc=peterz@infradead.org \
--cc=surenb@google.com \
--cc=tj@kernel.org \
/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
all inboxes | Powered by JetHome®