From: Tejun Heo <tj@kernel.org>
To: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Li Zefan <lizefan@huawei.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Paul Turner <pjt@google.com>
Cc: linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
kernel-team@fb.com
Subject: [PATCHSET REPOST] sched, cgroup: implement cgroup v2 interface for cpu controller
Date: Tue, 5 Jan 2016 11:47:58 -0500 [thread overview]
Message-ID: <20160105164758.GD5995@mtj.duckdns.org> (raw)
Hello,
This patchset implements cgroup v2 interface for cpu controller and a
repost of the following.
http://lkml.kernel.org/g/1438641689-14655-1-git-send-email-tj@kernel.org
The first patch is folded and applied into v2 documentation. The
second patch is unchanged. The third is unchanged from the posted v2.
The patchset got blocked by discussion on in-process hierarchical
resource contorl. The following message is to restart the discussion.
http://lkml.kernel.org/g/20160105154503.GC5995@mtj.duckdns.org
While the conclusion hasn't been reached, none of the issues being
debated affects the system level interface and there's no technical
reason to hold off these patches especially given that cgroup v2 is
being released in the coming merge window for memory and io
controllers.
Can we please go ahead with these?
diffstat follows.
kernel/sched/core.c | 149 +++++++++++++++++++++++++++++++++++++++++++++++--
kernel/sched/cpuacct.c | 57 ++++++++++++------
kernel/sched/cpuacct.h | 5 +
3 files changed, 189 insertions(+), 22 deletions(-)
Thanks.
--
tejun
next reply other threads:[~2016-01-05 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 16:47 Tejun Heo [this message]
2016-01-05 16:48 ` [PATCH 1/2] sched: Misc preps for cgroup unified hierarchy interface Tejun Heo
2016-01-05 16:48 ` [PATCH 2/2] sched: Implement interface for cgroup unified hierarchy 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=20160105164758.GD5995@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--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;
as well as URLs for NNTP newsgroup(s).