[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200301162003.GA186618@google.com>
Date: Sun, 1 Mar 2020 08:20:03 -0800
From: Marco Ballesio <balejs@...gle.com>
To: Roman Gushchin <guro@...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 Sat, Feb 29, 2020 at 10:43:00AM -0800, Roman Gushchin wrote:
> 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
Hi Roman,
When compared with backports of v2 features and their dependency chains, this
patch would be easier to carry in Android common. The potential is to have
killability for frozen processes on hw currently in use.
Marco
Powered by blists - more mailing lists