From: Tejun Heo <tj@kernel.org>
To: Roman Gushchin <guroan@gmail.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
kernel-team@fb.com, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org, Roman Gushchin <guro@fb.com>
Subject: Re: [PATCH v6 0/7] freezer for cgroup v2
Date: Thu, 24 Jan 2019 07:26:23 -0800 [thread overview]
Message-ID: <20190124152623.GH50184@devbig004.ftw2.facebook.com> (raw)
In-Reply-To: <20181222000307.28231-1-guro@fb.com>
On Fri, Dec 21, 2018 at 04:03:00PM -0800, Roman Gushchin wrote:
> This patchset implements freezer for cgroup v2.
>
> It provides similar functionality as v1 freezer, but the interface
> conforms to the cgroup v2 interface design principles, and it
> provides a better user experience: tasks can be killed, ptrace works,
> there is no separate controller, which has to be enabled, etc.
>
> Patches (1), (2) and (3) are some preparational work, patch (4) contains
> the implementation, patch (5) is a small cgroup kselftest fix,
> patch (6) covers freezer adds 6 new kselftests to cover the freezer
> functionality. Patch (7) adds corresponding docs.
>
> v6->v5:
> - reverted to clear TIF_SIGPENDING with additional checks before schedule(),
> as proposed by Oleg Nesterov
> - made cgroup v2 freezer working with the system freezer (by using
> freezable_schedule())
> - make freezer working with SIGSTOPped and PTRACEd tasks
> - added tests to cover freezing a cgroup with SIGSTOPped and PTRACEd tasks
Oleg, ping?
Thanks.
--
tejun
prev parent reply other threads:[~2019-01-24 15:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-22 0:03 [PATCH v6 0/7] freezer for cgroup v2 Roman Gushchin
2018-12-22 0:03 ` [PATCH v6 1/7] cgroup: rename freezer.c into legacy_freezer.c Roman Gushchin
2018-12-22 0:03 ` [PATCH v6 2/7] cgroup: implement __cgroup_task_count() helper Roman Gushchin
2018-12-22 0:03 ` [PATCH v6 3/7] cgroup: protect cgroup->nr_(dying_)descendants by css_set_lock Roman Gushchin
2018-12-22 0:03 ` [PATCH v6 4/7] cgroup: cgroup v2 freezer Roman Gushchin
2019-01-25 12:27 ` Oleg Nesterov
2019-01-25 13:46 ` Oleg Nesterov
2019-01-28 19:59 ` Roman Gushchin
2019-01-30 16:52 ` Oleg Nesterov
2019-02-11 21:30 ` Roman Gushchin
2019-02-14 16:26 ` Oleg Nesterov
2019-02-14 16:41 ` Roman Gushchin
2019-01-25 13:43 ` Oleg Nesterov
2018-12-22 0:03 ` [PATCH v6 5/7] kselftests: cgroup: don't fail on cg_kill_all() error in cg_destroy() Roman Gushchin
2018-12-22 0:03 ` Roman Gushchin
2018-12-22 0:03 ` guroan
2018-12-22 0:03 ` [PATCH v6 6/7] kselftests: cgroup: add freezer controller self-tests Roman Gushchin
2018-12-22 0:03 ` Roman Gushchin
2018-12-22 0:03 ` guroan
2018-12-22 0:03 ` [PATCH v6 7/7] cgroup: document cgroup v2 freezer interface Roman Gushchin
2019-01-24 15: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=20190124152623.GH50184@devbig004.ftw2.facebook.com \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=guro@fb.com \
--cc=guroan@gmail.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.