[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200324182615.GF162390@mtj.duckdns.org>
Date: Tue, 24 Mar 2020 14:26:15 -0400
From: Tejun Heo <tj@...nel.org>
To: Marco Ballesio <balejs@...gle.com>
Cc: Daniel Colascione <dancol@...gle.com>,
Roman Gushchin <guro@...com>, cgroups@...r.kernel.org,
linux-kernel <linux-kernel@...r.kernel.org>, lizefan@...wei.com,
Johannes Weiner <hannes@...xchg.org>,
Jonathan Corbet <corbet@....net>, rjw@...ysocki.net,
Pavel Machek <pavel@....cz>, len.brown@...el.com,
"open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
linux-pm@...r.kernel.org, Minchan Kim <minchan@...gle.com>,
Suren Baghdasaryan <surenb@...gle.com>
Subject: Re: [PATCH] cgroup-v1: freezer: optionally killable freezer
Hello,
On Fri, Mar 20, 2020 at 01:10:38PM -0700, Marco Ballesio wrote:
> It might also be desirable for userland to have a way to modify the behavior of
> an already mounted v1 freezer.
>
> Tejun, would it be acceptable to have a flag but disable it by default, hiding
> it behind a kernel configuration option?
Given how dead-end this is, I'm not sure this needs to be upstream. Can you give
me some rationales?
Thanks.
--
tejun
Powered by blists - more mailing lists