From: Tejun Heo <tj@kernel.org>
To: lizefan@huawei.com
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
vgoyal@redhat.com, axboe@kernel.dk, hannes@cmpxchg.org,
mhocko@suse.cz, arozansk@redhat.com
Subject: [PATCHSET cgroup/for-3.16] cgroup: implement cftype->write()
Date: Tue, 6 May 2014 08:44:21 -0400 [thread overview]
Message-ID: <1399380266-3324-1-git-send-email-tj@kernel.org> (raw)
Hello,
This patchset implements a new cftype operation ->write() and replace
->write_string() and ->trigger() with it. ->write() is similar to
->write_string() but maps directly to the kernfs write operation and
has access to all available context information including the
associated kernfs_open_file, which will make things like implementing
kernfs active protection manipulation easier.
->write_string() becomes redundant and ->trigger() has always been
spurious. This patch replaces all users of the two methods to
->write() and remove them.
This patchset contains the following five patches.
0001-cgroup-implement-cftype-write.patch
0002-cgroup-replace-cftype-write_string-with-cftype-write.patch
0003-cgroup-replace-cftype-trigger-with-cftype-write.patch
0004-cgroup-convert-tasks-and-cgroup.procs-handle-to-use-.patch
0005-cgroup-remove-cgroup-control_kn.patch
0001 implements cftype->write().
0002-0003 replace cftype->write_string() and ->trigger() with it.
0004 convert "tasks" and "cgroup.procs" handler too.
0005 removes cgroup->control_kn as the kernfs_node is now directly
accessible from kernfs_open_file.
This patchset is on top of
cgroup/for-3.16 12d3089c192c ("kernel/cpuset.c: convert printk to pr_foo()")
+ [1] [PATCHSET cgroup/for-3.16] cgroup: post unified hierarchy fixes and updates
and available on the following git branch.
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git review-post-unified-updates
diffstat follows.
block/blk-throttle.c | 32 ++++++++---------
block/cfq-iosched.c | 28 +++++++--------
include/linux/cgroup.h | 40 +++++++++++----------
kernel/cgroup.c | 85 +++++++++++++++++++++++-----------------------
kernel/cgroup_freezer.c | 20 ++++------
kernel/cpuset.c | 16 ++++----
mm/hugetlb_cgroup.c | 33 +++++++++--------
mm/memcontrol.c | 80 +++++++++++++++++++++++--------------------
net/ipv4/tcp_memcontrol.c | 31 +++++++++-------
security/device_cgroup.c | 14 +++----
10 files changed, 197 insertions(+), 182 deletions(-)
Thanks.
--
tejun
[1] http://lkml.kernel.org/g/1399377044-29873-1-git-send-email-tj@kernel.org
next reply other threads:[~2014-05-06 12:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 12:44 Tejun Heo [this message]
2014-05-06 12:44 ` [PATCH 1/5] cgroup: implement cftype->write() Tejun Heo
2014-05-06 12:44 ` [PATCH 2/5] cgroup: replace cftype->write_string() with cftype->write() Tejun Heo
2014-05-06 12:54 ` Aristeu Rozanski
2014-05-06 14:07 ` [PATCH v2 " Tejun Heo
2014-05-08 19:35 ` [PATCH " Vivek Goyal
2014-05-06 12:44 ` [PATCH 3/5] cgroup: replace cftype->trigger() " Tejun Heo
2014-05-06 12:44 ` [PATCH 4/5] cgroup: convert "tasks" and "cgroup.procs" handle to use cftype->write() Tejun Heo
2014-05-06 12:44 ` [PATCH 5/5] cgroup: remove cgroup->control_kn Tejun Heo
2014-05-09 19:50 ` [PATCHSET cgroup/for-3.16] cgroup: implement cftype->write() Tejun Heo
2014-05-13 6:34 ` Li Zefan
2014-05-13 16:17 ` 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=1399380266-3324-1-git-send-email-tj@kernel.org \
--to=tj@kernel.org \
--cc=arozansk@redhat.com \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mhocko@suse.cz \
--cc=vgoyal@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox