[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200229184300.GA484762@carbon.DHCP.thefacebook.com>
Date: Sat, 29 Feb 2020 10:43:00 -0800
From: Roman Gushchin <guro@...com>
To: Marco Ballesio <balejs@...gle.com>
CC: <tj@...nel.org>, <cgroups@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <lizefan@...wei.com>,
<hannes@...xchg.org>, <corbet@....net>, <rjw@...ysocki.net>,
<pavel@....cz>, <len.brown@...el.com>, <linux-doc@...r.kernel.org>,
<linux-pm@...r.kernel.org>, <minchan@...gle.com>,
<surenb@...gle.com>, <dancol@...gle.com>
Subject: Re: [PATCH] cgroup-v1: freezer: optionally killable freezer
On Fri, Feb 28, 2020 at 04:51:31PM -0800, Marco Ballesio wrote:
> Hi all,
>
> did anyone have time to look into my proposal and, in case, are there
> any suggestions, ideas or comments about it?
Hello, Marco!
I'm sorry, somehow I missed the original letter.
In general the cgroup v1 interface is considered frozen. Are there any particular
reasons why you want to extend the v1 freezer rather than use the v2 version of it?
You don't even need to fully convert to cgroup v2 in order to do it, some v1
controllers can still be used.
Thanks!
Roman
Powered by blists - more mailing lists