From: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: nishimura@mxp.nes.nec.co.jp, linux-mm <linux-mm@kvack.org>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Paul Menage <menage@google.com>, Li Zefan <lizf@cn.fujitsu.com>
Subject: Re: [RFC][PATCH 1/8] cgroup: introduce cancel_attach()
Date: Fri, 25 Sep 2009 08:39:54 +0900 [thread overview]
Message-ID: <20090925083954.90baa2b0.nishimura@mxp.nes.nec.co.jp> (raw)
In-Reply-To: <20090924153309.ed78007f.kamezawa.hiroyu@jp.fujitsu.com>
On Thu, 24 Sep 2009 15:33:09 +0900, KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> On Thu, 24 Sep 2009 14:43:27 +0900
> Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
>
> > This patch adds cancel_attach() operation to struct cgroup_subsys.
> > cancel_attach() can be used when can_attach() operation prepares something
> > for the subsys, but we should discard what can_attach() operation has prepared
> > if attach task/proc fails afterwards.
> >
> > Signed-off-by: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
> > ---
> > Documentation/cgroups/cgroups.txt | 12 ++++++++++++
> > include/linux/cgroup.h | 2 ++
> > kernel/cgroup.c | 36 ++++++++++++++++++++++++++++--------
> > 3 files changed, 42 insertions(+), 8 deletions(-)
> >
> > diff --git a/Documentation/cgroups/cgroups.txt b/Documentation/cgroups/cgroups.txt
> > index 3df4b9a..07bb678 100644
> > --- a/Documentation/cgroups/cgroups.txt
> > +++ b/Documentation/cgroups/cgroups.txt
> > @@ -544,6 +544,18 @@ remain valid while the caller holds cgroup_mutex. If threadgroup is
> > true, then a successful result indicates that all threads in the given
> > thread's threadgroup can be moved together.
> >
> > +void cancel_attach(struct cgroup_subsys *ss, struct cgroup *cgrp,
> > + struct task_struct *task, bool threadgroup)
> > +(cgroup_mutex held by caller)
> > +
> > +Called when a task attach operation has failed after can_attach() has succeeded.
> > +For example, this will be called if some subsystems are mounted on the same
> > +hierarchy, can_attach() operations have succeeded about part of the subsystems,
> > +but has failed about next subsystem. This will be called only about subsystems
> > +whose can_attach() operation has succeeded. This may be useful for subsystems
> > +which prepare something in can_attach() operation but should discard what has
> > +been prepared on failure.
> > +
>
> Hmm..I'd like to add a text like this ..
> ==
> +A subsystem whose can_attach() has some side-effects should provide this function.
> +Then, the subsytem can implement a rollback. If not, not necessary.
> ==
>
O.K.
will add in next post.
> > void attach(struct cgroup_subsys *ss, struct cgroup *cgrp,
> > struct cgroup *old_cgrp, struct task_struct *task,
> > bool threadgroup)
> > diff --git a/include/linux/cgroup.h b/include/linux/cgroup.h
> > index 642a47f..a08edbc 100644
> > --- a/include/linux/cgroup.h
> > +++ b/include/linux/cgroup.h
> > @@ -429,6 +429,8 @@ struct cgroup_subsys {
> > void (*destroy)(struct cgroup_subsys *ss, struct cgroup *cgrp);
> > int (*can_attach)(struct cgroup_subsys *ss, struct cgroup *cgrp,
> > struct task_struct *tsk, bool threadgroup);
> > + void (*cancel_attach)(struct cgroup_subsys *ss, struct cgroup *cgrp,
> > + struct task_struct *tsk, bool threadgroup);
> > void (*attach)(struct cgroup_subsys *ss, struct cgroup *cgrp,
> > struct cgroup *old_cgrp, struct task_struct *tsk,
> > bool threadgroup);
> > diff --git a/kernel/cgroup.c b/kernel/cgroup.c
> > index 7da6004..2d9a808 100644
> > --- a/kernel/cgroup.c
> > +++ b/kernel/cgroup.c
> > @@ -1700,7 +1700,7 @@ void threadgroup_fork_unlock(struct sighand_struct *sighand)
> > int cgroup_attach_task(struct cgroup *cgrp, struct task_struct *tsk)
> > {
> > int retval;
> > - struct cgroup_subsys *ss;
> > + struct cgroup_subsys *ss, *fail = NULL;
> > struct cgroup *oldcgrp;
> > struct cgroupfs_root *root = cgrp->root;
> >
> > @@ -1712,14 +1712,16 @@ int cgroup_attach_task(struct cgroup *cgrp, struct task_struct *tsk)
> > for_each_subsys(root, ss) {
> > if (ss->can_attach) {
> > retval = ss->can_attach(ss, cgrp, tsk, false);
> > - if (retval)
> > - return retval;
> > + if (retval) {
> > + fail = ss;
> > + goto out;
> > + }
> > }
> > }
> >
> > retval = cgroup_task_migrate(cgrp, oldcgrp, tsk, 0);
> > if (retval)
> > - return retval;
> > + goto out;
> >
>
> Hmm...maybe we don't have this code in the latest tree.
> Ah...ok, this is from
> cgroups-add-ability-to-move-all-threads-in-a-process-to-a-new-cgroup-atomically
> .patch
> which is now hidden.
>
Indeed.. these part are different now.
My patches are based on mmotm-2009-09-14-01-57, I'm sorry for cunfusing you.
Thanks,
Daisuke Nishimura.
>
>
> > for_each_subsys(root, ss) {
> > if (ss->attach)
> > @@ -1733,7 +1735,15 @@ int cgroup_attach_task(struct cgroup *cgrp, struct task_struct *tsk)
> > * is no longer empty.
> > */
> > cgroup_wakeup_rmdir_waiter(cgrp);
> > - return 0;
> > +out:
> > + if (retval)
> > + for_each_subsys(root, ss) {
> > + if (ss == fail)
> > + break;
> > + if (ss->cancel_attach)
> > + ss->cancel_attach(ss, cgrp, tsk, false);
> > + }
> > + return retval;
> > }
> >
> > /*
> > @@ -1813,7 +1823,7 @@ static int css_set_prefetch(struct cgroup *cgrp, struct css_set *cg,
> > int cgroup_attach_proc(struct cgroup *cgrp, struct task_struct *leader)
> > {
> > int retval;
> > - struct cgroup_subsys *ss;
> > + struct cgroup_subsys *ss, *fail = NULL;
> > struct cgroup *oldcgrp;
> > struct css_set *oldcg;
> > struct cgroupfs_root *root = cgrp->root;
> > @@ -1839,8 +1849,10 @@ int cgroup_attach_proc(struct cgroup *cgrp, struct task_struct *leader)
> > for_each_subsys(root, ss) {
> > if (ss->can_attach) {
> > retval = ss->can_attach(ss, cgrp, leader, true);
> > - if (retval)
> > - return retval;
> > + if (retval) {
> > + fail = ss;
> > + goto out;
> > + }
> > }
> > }
> >
> > @@ -1978,6 +1990,14 @@ list_teardown:
> > put_css_set(cg_entry->cg);
> > kfree(cg_entry);
> > }
> > +out:
> > + if (retval)
> > + for_each_subsys(root, ss) {
> > + if (ss == fail)
> > + break;
> > + if (ss->cancel_attach)
> > + ss->cancel_attach(ss, cgrp, tsk, true);
> > + }
> > /* done! */
> > return retval;
> > }
>
> No objections from me. just wait for comments from Paul or Li.
>
> I wonder if we add cancel_attach(), can_attach() should be renamed to
> prepare_attach() or some. ;)
>
>
> Thanks,
> -Kame
>
>
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-09-24 23:51 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 2:23 [RFC][EXPERIMENTAL][PATCH 0/8] memcg: migrate charge at task move Daisuke Nishimura
2009-09-17 2:24 ` [PATCH 1/8] memcg: introduce mem_cgroup_cancel_charge() Daisuke Nishimura
2009-09-17 4:12 ` KAMEZAWA Hiroyuki
2009-09-17 2:24 ` [PATCH 2/8] memcg: cleanup mem_cgroup_move_parent() Daisuke Nishimura
2009-09-17 4:15 ` KAMEZAWA Hiroyuki
2009-09-17 2:25 ` [PATCH 3/8] cgroup: introduce cancel_attach() Daisuke Nishimura
2009-09-17 2:26 ` [PATCH 4/8] memcg: add interface to migrate charge Daisuke Nishimura
2009-09-17 4:20 ` KAMEZAWA Hiroyuki
2009-09-17 4:40 ` Daisuke Nishimura
2009-09-17 2:26 ` [PATCH 5/8] memcg: migrate charge of anon Daisuke Nishimura
2009-09-17 4:57 ` KAMEZAWA Hiroyuki
2009-09-17 5:56 ` Daisuke Nishimura
2009-09-17 6:25 ` KAMEZAWA Hiroyuki
2009-09-17 23:52 ` KOSAKI Motohiro
2009-09-17 2:27 ` [PATCH 6/8] memcg: migrate charge of shmem Daisuke Nishimura
2009-09-17 5:02 ` KAMEZAWA Hiroyuki
2009-09-17 2:28 ` [PATCH 7/8] memcg: migrate charge of swap Daisuke Nishimura
2009-09-17 5:25 ` KAMEZAWA Hiroyuki
2009-09-17 6:17 ` Daisuke Nishimura
2009-09-17 6:28 ` KAMEZAWA Hiroyuki
2009-09-17 2:29 ` [PATCH 8/8] memcg: avoid oom during charge migration Daisuke Nishimura
2009-09-17 7:01 ` [RFC][EXPERIMENTAL][PATCH 0/8] memcg: migrate charge at task move Daisuke Nishimura
2009-09-24 5:42 ` [RFC][PATCH 0/8] memcg: migrate charge at task move (24/Sep) Daisuke Nishimura
2009-09-24 5:43 ` [RFC][PATCH 1/8] cgroup: introduce cancel_attach() Daisuke Nishimura
2009-09-24 6:33 ` KAMEZAWA Hiroyuki
2009-09-24 23:39 ` Daisuke Nishimura [this message]
2009-09-24 5:44 ` [RFC][PATCH 2/8] memcg: introduce mem_cgroup_cancel_charge() Daisuke Nishimura
2009-09-24 5:46 ` [RFC][PATCH 3/8] memcg: cleanup mem_cgroup_move_parent() Daisuke Nishimura
2009-09-24 6:37 ` KAMEZAWA Hiroyuki
2009-09-24 6:54 ` Daisuke Nishimura
2009-09-24 5:47 ` [RFC][PATCH 4/8] memcg: add interface to migrate charge Daisuke Nishimura
2009-09-24 6:54 ` KAMEZAWA Hiroyuki
2009-09-24 23:39 ` Daisuke Nishimura
2009-09-24 5:48 ` [RFC][PATCH 5/8] memcg: migrate charge of mapped page Daisuke Nishimura
2009-09-24 7:22 ` KAMEZAWA Hiroyuki
2009-09-24 8:00 ` Daisuke Nishimura
2009-09-25 0:28 ` Daisuke Nishimura
2009-09-25 0:49 ` KAMEZAWA Hiroyuki
2009-09-24 5:49 ` [RFC][PATCH 6/8] memcg: avoid oom during charge migration Daisuke Nishimura
2009-09-24 7:34 ` KAMEZAWA Hiroyuki
2009-09-25 1:44 ` Daisuke Nishimura
2009-09-25 1:55 ` KAMEZAWA Hiroyuki
2009-09-25 4:51 ` Daisuke Nishimura
2009-09-25 5:36 ` Daisuke Nishimura
2009-09-25 5:52 ` KAMEZAWA Hiroyuki
2009-09-24 5:49 ` [RFC][PATCH 7/8] memcg: migrate charge of swap Daisuke Nishimura
2009-09-24 5:50 ` [RFC][PATCH 8/8] memcg: migrate charge of shmem swap Daisuke Nishimura
2009-09-24 7:41 ` KAMEZAWA Hiroyuki
2009-09-25 0:28 ` Daisuke Nishimura
2009-10-13 4:49 [RFC][PATCH 0/8] memcg: recharge at task move (Oct13) Daisuke Nishimura
2009-10-13 4:50 ` [RFC][PATCH 1/8] cgroup: introduce cancel_attach() Daisuke Nishimura
2009-10-15 7:37 ` Paul Menage
2009-10-15 8:50 ` Paul Menage
2009-10-15 11:08 ` Daisuke Nishimura
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=20090925083954.90baa2b0.nishimura@mxp.nes.nec.co.jp \
--to=nishimura@mxp.nes.nec.co.jp \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.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