From: Tejun Heo <tj@kernel.org>
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, john@johnmccutchan.com,
rlove@rlove.org, eparis@parisplace.org, serge.hallyn@ubuntu.com,
lennart@poettering.net, kay@vrfy.org, lizefan@huawei.com,
cgroups@vger.kernel.org, containers@lists.linux-foundation.org
Subject: [PATCHSET cgroup/for-3.16] cgroup: implement cgroup.populated
Date: Wed, 9 Apr 2014 11:07:29 -0400 [thread overview]
Message-ID: <1397056052-2829-1-git-send-email-tj@kernel.org> (raw)
Hello,
(inotify folks, can you please review the second patch which hooks up
kernfs_notify() with fsnotify? It works but directly invoking
fsnotify_parent() and fsnotify() feels a bit dirty. Maybe something
like fsnotify_notify_modify_by_dentry() would make more sense?)
cgroup users often need a way to determine when a cgroup's
subhierarchy becomes empty so that it can be cleaned up. cgroup
currently provides release_agent for it; unfortunately, this mechanism
is riddled with issues. This patchset implements a replacement
mechanism "cgroup.subtree_populated" which can be used to monitor
whether the cgroup's subhierarchy has tasks in it or not and triggers
poll and [di]notify events when its content changes.
This patchset contains the following three patches.
0001-kernfs-implement-kernfs_root-supers-list.patch
0002-kernfs-make-kernfs_notify-trigger-inotify-events-too.patch
0003-cgroup-implement-cgroup.subtree_populated-for-the-de.patch
0001-0002 add [di]notify notification to kernfs_notify().
0003 implements cgroup.subtree_populated.
This patchset is on top of "cgroup: implement unified hierarchy"
patchset[1] and availalbe in the following git branch.
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git review-populated
diffstat follows.
fs/kernfs/dir.c | 1
fs/kernfs/file.c | 41 +++++++++++++++++++++++----
fs/kernfs/kernfs-internal.h | 5 +++
fs/kernfs/mount.c | 11 +++++++
include/linux/cgroup.h | 15 ++++++++++
include/linux/kernfs.h | 4 ++
kernel/cgroup.c | 65 +++++++++++++++++++++++++++++++++++++++++---
7 files changed, 132 insertions(+), 10 deletions(-)
--
tejun
[1] http://lkml.kernel.org/g/1395974461-12735-1-git-send-email-tj@kernel.org
next reply other threads:[~2014-04-09 15:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 15:07 Tejun Heo [this message]
2014-04-09 15:07 ` [PATCH 1/3] kernfs: implement kernfs_root->supers list Tejun Heo
2014-04-09 15:07 ` [PATCH 2/3] kernfs: make kernfs_notify() trigger inotify events too Tejun Heo
2014-04-09 15:07 ` [PATCH 3/3] cgroup: implement cgroup.subtree_populated for the default hierarchy Tejun Heo
2014-04-10 3:08 ` Serge E. Hallyn
2014-04-10 13:08 ` Tejun Heo
2014-04-10 14:04 ` Serge Hallyn
2014-04-10 14:19 ` Tejun Heo
2014-04-11 9:00 ` Li Zefan
2014-04-14 21:31 ` [PATCHSET cgroup/for-3.16] cgroup: implement cgroup.populated Tejun Heo
2014-04-14 22:26 ` Greg KH
2014-04-15 16:18 ` Tejun Heo
2014-04-23 15:16 ` Tejun Heo
2014-04-25 18:57 ` Greg KH
2014-04-25 22:30 ` 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=1397056052-2829-1-git-send-email-tj@kernel.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=eparis@parisplace.org \
--cc=gregkh@linuxfoundation.org \
--cc=john@johnmccutchan.com \
--cc=kay@vrfy.org \
--cc=lennart@poettering.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=rlove@rlove.org \
--cc=serge.hallyn@ubuntu.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