From: Li Zefan <lizf@cn.fujitsu.com>
To: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Cc: linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Paul Menage <menage@google.com>
Subject: Re: [PATCH -mmotm 1/8] cgroup: introduce cancel_attach()
Date: Mon, 09 Nov 2009 15:23:02 +0800 [thread overview]
Message-ID: <4AF7C356.5020504@cn.fujitsu.com> (raw)
In-Reply-To: <20091106141106.a2bd995a.nishimura@mxp.nes.nec.co.jp>
Daisuke Nishimura 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 rollback what can_attach() operation has prepared
> if attach task fails after we've succeeded in can_attach().
>
> Signed-off-by: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Acked-by: Li Zefan <lizf@cn.fujitsu.com>
> ---
> Documentation/cgroups/cgroups.txt | 13 +++++++++++-
> include/linux/cgroup.h | 2 +
> kernel/cgroup.c | 38 ++++++++++++++++++++++++++++++------
> 3 files changed, 45 insertions(+), 8 deletions(-)
>
> diff --git a/Documentation/cgroups/cgroups.txt b/Documentation/cgroups/cgroups.txt
> index 0b33bfe..c86947c 100644
> --- a/Documentation/cgroups/cgroups.txt
> +++ b/Documentation/cgroups/cgroups.txt
> @@ -536,10 +536,21 @@ returns an error, this will abort the attach operation. If a NULL
> task is passed, then a successful result indicates that *any*
> unspecified task can be moved into the cgroup. Note that this isn't
> called on a fork. If this method returns 0 (success) then this should
> -remain valid while the caller holds cgroup_mutex. If threadgroup is
> +remain valid while the caller holds cgroup_mutex and it is ensured that either
> +attach() or cancel_attach() will be called in futer. If threadgroup is
s/futer/future
> true, then a successful result indicates that all threads in the given
> thread's threadgroup can be moved together.
...
> +out:
> + if (retval)
I prefer:
if (reval) {
...
}
> + for_each_subsys(root, ss) {
> + if (ss == failed_ss)
> + /*
> + * This means can_attach() of this subsystem
> + * have failed, so we don't need to call
> + * cancel_attach() against rests of subsystems.
> + */
> + break;
> + if (ss->cancel_attach)
> + ss->cancel_attach(ss, cgrp, tsk, false);
> + }
> + return retval;
> }
>
> /*
--
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-11-09 7:24 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 5:10 [PATCH -mmotm 0/8] memcg: recharge at task move Daisuke Nishimura
2009-11-06 5:11 ` [PATCH -mmotm 1/8] cgroup: introduce cancel_attach() Daisuke Nishimura
2009-11-09 6:57 ` Balbir Singh
2009-11-09 7:18 ` Li Zefan
2009-11-09 7:23 ` Daisuke Nishimura
2009-11-09 7:23 ` Li Zefan [this message]
2009-11-09 7:38 ` Daisuke Nishimura
2009-11-06 5:11 ` [PATCH -mmotm 2/8] memcg: move memcg_tasklist mutex Daisuke Nishimura
2009-11-06 5:54 ` KAMEZAWA Hiroyuki
2009-11-06 7:49 ` Daisuke Nishimura
2009-11-06 8:02 ` KAMEZAWA Hiroyuki
2009-11-10 19:14 ` Balbir Singh
2009-11-10 23:44 ` Daisuke Nishimura
2009-11-06 5:12 ` [PATCH -mmotm 3/8] memcg: add mem_cgroup_cancel_charge() Daisuke Nishimura
2009-11-06 5:13 ` [PATCH -mmotm 4/8] memcg: cleanup mem_cgroup_move_parent() Daisuke Nishimura
2009-11-06 5:56 ` KAMEZAWA Hiroyuki
2009-11-06 5:14 ` [PATCH -mmotm 5/8] memcg: add interface to recharge at task move Daisuke Nishimura
2009-11-06 6:06 ` KAMEZAWA Hiroyuki
2009-11-06 5:14 ` [PATCH -mmotm 6/8] memcg: recharge charges of anonymous page Daisuke Nishimura
2009-11-06 6:35 ` KAMEZAWA Hiroyuki
2009-11-09 0:31 ` Daisuke Nishimura
2009-11-06 5:15 ` [PATCH -mmotm 7/8] memcg: avoid oom during recharge at task move Daisuke Nishimura
2009-11-06 6:39 ` KAMEZAWA Hiroyuki
2009-11-06 5:16 ` [PATCH -mmotm 8/8] memcg: recharge charges of anonymous swap Daisuke Nishimura
2009-11-06 6:45 ` [PATCH -mmotm 0/8] memcg: recharge at task move KAMEZAWA Hiroyuki
2009-11-09 1:44 ` Daisuke Nishimura
2009-11-09 5:16 ` KAMEZAWA Hiroyuki
2009-11-09 5:08 ` Balbir Singh
2009-11-09 8:24 ` Daisuke Nishimura
2009-11-11 1:35 ` [PATCH -mmotm 0/3] some cleanups for memcg Daisuke Nishimura
2009-11-11 1:36 ` [PATCH -mmotm 1/3] memcg: add mem_cgroup_cancel_charge() Daisuke Nishimura
2009-11-11 4:24 ` Balbir Singh
2009-11-11 1:37 ` [PATCH -mmotm 2/3] memcg: cleanup mem_cgroup_move_parent() Daisuke Nishimura
2009-11-11 14:40 ` Balbir Singh
2009-11-11 15:16 ` Daisuke Nishimura
2009-11-11 1:39 ` [PATCH -mmotm 3/3] memcg: remove memcg_tasklist Daisuke Nishimura
2009-11-11 1:49 ` KAMEZAWA Hiroyuki
2009-11-11 16:01 ` Balbir Singh
2009-11-12 8:05 ` Daisuke Nishimura
2009-12-14 6:17 [PATCH -mmotm 0/8] memcg: move charge at task migration (14/Dec) Daisuke Nishimura
2009-12-14 6:18 ` [PATCH -mmotm 1/8] cgroup: introduce cancel_attach() Daisuke Nishimura
2009-12-21 5:31 [PATCH -mmotm 0/8] memcg: move charge at task migration (21/Dec) Daisuke Nishimura
2009-12-21 5:32 ` [PATCH -mmotm 1/8] cgroup: introduce cancel_attach() 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=4AF7C356.5020504@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=menage@google.com \
--cc=nishimura@mxp.nes.nec.co.jp \
/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