From: Tejun Heo <tj@kernel.org>
To: lizefan@huawei.com, hannes@cmpxchg.org, peterz@infradead.org,
mingo@redhat.com, longman@redhat.com
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@fb.com, pjt@google.com, luto@amacapital.net,
efault@gmx.de, torvalds@linux-foundation.org, guro@fb.com
Subject: [PATCHSET for-4.13] cgroup: implement cgroup2 thread mode, v4
Date: Wed, 19 Jul 2017 15:44:33 -0400 [thread overview]
Message-ID: <20170719194439.2915602-1-tj@kernel.org> (raw)
Hello,
This is v4 of cgroup2 thread mode patchset. The changes from v3[L]
are all fairly minor. Peter and Waiman are okay with the approach and
I'll apply these patches to cgorup/for-4.14 unless there are further
objections. Please speak up if there are any further concerns.
* Documentation updates as suggested by Waiman.
* () dropped from cgroup.type output.
* Other minor fixes and updates.
* Tried to add "threaded" column to /proc/cgroups but systemd fails to
parse and boot if the field is added. I don't think we can ever add
new field to that file. I'll probably add
cgroup.threaded_controllers file. It's nicer to contain the
information inside cgroupfs anyway. Will follow up on this.
It is largely based on the discussions that we had at the plumbers
last year. Here's the rough outline.
* Thread mode is explicitly enabled on a cgroup by writing "threaded"
into "cgroup.type" file. The cgroup shouldn't have any processes or
child cgroups. A threaded cgroup joins the the parent's resource
domain and becomes a part of the threaded subtree anchored at the
nearest domain ancestor, which is called the threaded domain cgroup
of the subtree.
* Threads can be put anywhere in a threaded subtree by writing TIDs
into "cgroup.threads" file. Process granularity and
no-internal-process constraint don't apply in a threaded subtree.
* To be used in a threaded subtree, controllers should explicitly
declare thread mode support and should be able to handle internal
competition in some way.
* The threaded domain cgroup of a threaded subtree serves as the
resource domain for the whole subtree. This is where all the
controllers are guaranteed to have a common ground and resource
consumptions in the threaded subtree which aren't tied to a specific
thread are charged. Non-threaded controllers never see beyond
thread root and can assume that all controllers will follow the same
rules upto that point.
* Unlike other cgroups, the system root cgroup can serve as parent to
domain child cgroups and threaded domains to threaded subtrees.
This allows threaded controllers to implement thread granular resource
control without getting in the way of system level resource
partitioning.
For more details on the interface and behavior, please refer to 0005.
This patchset contains the following six patches.
0001-cgroup-reorganize-cgroup.procs-task-write-path.patch
0002-cgroup-add-flags-to-css_task_iter_start-and-implemen.patch
0003-cgroup-introduce-cgroup-dom_cgrp-and-threaded-css_se.patch
0004-cgroup-implement-CSS_TASK_ITER_THREADED.patch
0005-cgroup-implement-cgroup-v2-thread-support.patch
0006-cgroup-update-debug-controller-to-print-out-thread-m.patch
0001-0005 implement cgroup2 thread mode. 0006 enables debug
controller on it.
The patchset is based on the current cgroup/for-4.14 27f26753f8c0
("cgroup: replace css_set walking populated test with testing
cgrp->nr_populated_csets") and also available in the following git
branch.
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git review-cgroup2-threads-v4
diffstat follows.
Documentation/cgroup-v2.txt | 185 +++++++++-
include/linux/cgroup-defs.h | 45 ++
include/linux/cgroup.h | 15
kernel/cgroup/cgroup-internal.h | 12
kernel/cgroup/cgroup-v1.c | 69 +++
kernel/cgroup/cgroup.c | 711 +++++++++++++++++++++++++++++++---------
kernel/cgroup/cpuset.c | 6
kernel/cgroup/debug.c | 53 ++
kernel/cgroup/freezer.c | 6
kernel/cgroup/pids.c | 1
kernel/events/core.c | 1
mm/memcontrol.c | 2
net/core/netclassid_cgroup.c | 2
13 files changed, 904 insertions(+), 204 deletions(-)
Thanks.
--
tejun
[L] http://lkml.kernel.org/r/20170717020721.3612468-1-tj@kernel.org
next reply other threads:[~2017-07-19 19:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 19:44 Tejun Heo [this message]
2017-07-19 19:44 ` [PATCH 1/6] cgroup: reorganize cgroup.procs / task write path Tejun Heo
2017-07-19 19:44 ` [PATCH 2/6] cgroup: add @flags to css_task_iter_start() and implement CSS_TASK_ITER_PROCS Tejun Heo
2017-07-19 19:44 ` [PATCH 3/6] cgroup: introduce cgroup->dom_cgrp and threaded css_set handling Tejun Heo
2017-07-19 19:44 ` [PATCH 4/6] cgroup: implement CSS_TASK_ITER_THREADED Tejun Heo
2017-07-19 19:44 ` [PATCH 5/6] cgroup: implement cgroup v2 thread support Tejun Heo
2017-07-19 19:44 ` [PATCH 6/6] cgroup: update debug controller to print out thread mode information Tejun Heo
2017-07-21 15:18 ` [PATCHSET for-4.13] cgroup: implement cgroup2 thread mode, v4 Tejun Heo
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=20170719194439.2915602-1-tj@kernel.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=efault@gmx.de \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=longman@redhat.com \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=torvalds@linux-foundation.org \
/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