From: Tejun Heo <tj@kernel.org>
To: Marco Ballesio <balejs@google.com>
Cc: Daniel Colascione <dancol@google.com>,
Roman Gushchin <guro@fb.com>,
cgroups@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
lizefan@huawei.com, Johannes Weiner <hannes@cmpxchg.org>,
Jonathan Corbet <corbet@lwn.net>,
rjw@rjwysocki.net, Pavel Machek <pavel@ucw.cz>,
len.brown@intel.com,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
linux-pm@vger.kernel.org, Minchan Kim <minchan@google.com>,
Suren Baghdasaryan <surenb@google.com>
Subject: Re: [PATCH] cgroup-v1: freezer: optionally killable freezer
Date: Tue, 24 Mar 2020 14:26:15 -0400 [thread overview]
Message-ID: <20200324182615.GF162390@mtj.duckdns.org> (raw)
In-Reply-To: <20200320201038.GB79184@google.com>
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
prev parent reply other threads:[~2020-03-24 18:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 18:32 [PATCH] cgroup-v1: freezer: optionally killable freezer Marco Ballesio
[not found] ` <20200219183231.50985-1-balejs-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2020-02-29 0:51 ` Marco Ballesio
[not found] ` <20200229005131.GB9813-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2020-02-29 18:43 ` Roman Gushchin
[not found] ` <20200229184300.GA484762-lLJQVQxiE4uLfgCeKHXN1g2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
2020-03-01 16:20 ` Marco Ballesio
[not found] ` <20200301162003.GA186618-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2020-03-02 16:53 ` Roman Gushchin
2020-03-02 17:46 ` Suren Baghdasaryan
2020-03-02 18:27 ` Roman Gushchin
2020-03-03 13:48 ` Tejun Heo
2020-03-11 17:46 ` Daniel Colascione
2020-03-20 20:10 ` Marco Ballesio
2020-03-24 18:26 ` Tejun Heo [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=20200324182615.GF162390@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=balejs@google.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=dancol@google.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=len.brown@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=minchan@google.com \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=surenb@google.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;
as well as URLs for NNTP newsgroup(s).