From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: balbir@linux.vnet.ibm.com
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: [RFC][2/3] memcg safe operaton for checking a cgroup is under move accounts
Date: Wed, 2 Jun 2010 09:37:32 +0900 [thread overview]
Message-ID: <20100602093732.1026eaf3.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20100601112529.GE2804@balbir.in.ibm.com>
On Tue, 1 Jun 2010 16:55:29 +0530
Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> * KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> [2010-06-01 18:27:20]:
>
> > From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> >
> > Now, for checking a memcg is under task-account-moving, we do css_tryget()
> > against mc.to and mc.from. But this ust complicates things. This patch
> > makes the check easier. (And I doubt the current code has some races..)
> >
> > This patch adds a spinlock to move_charge_struct and guard modification
> > of mc.to and mc.from. By this, we don't have to think about complicated
> > races around this not-critical path.
> >
> > Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> > ---
> > mm/memcontrol.c | 48 ++++++++++++++++++++++++++++--------------------
> > 1 file changed, 28 insertions(+), 20 deletions(-)
> >
> > Index: mmotm-2.6.34-May21/mm/memcontrol.c
> > ===================================================================
> > --- mmotm-2.6.34-May21.orig/mm/memcontrol.c
> > +++ mmotm-2.6.34-May21/mm/memcontrol.c
> > @@ -268,6 +268,7 @@ enum move_type {
> >
> > /* "mc" and its members are protected by cgroup_mutex */
> > static struct move_charge_struct {
> > + spinlock_t lock; /* for from, to, moving_task */
> > struct mem_cgroup *from;
> > struct mem_cgroup *to;
> > unsigned long precharge;
> > @@ -276,6 +277,7 @@ static struct move_charge_struct {
> > struct task_struct *moving_task; /* a task moving charges */
> > wait_queue_head_t waitq; /* a waitq for other context */
> > } mc = {
> > + .lock = __SPIN_LOCK_UNLOCKED(mc.lock),
> > .waitq = __WAIT_QUEUE_HEAD_INITIALIZER(mc.waitq),
> > };
> >
> > @@ -1076,26 +1078,25 @@ static unsigned int get_swappiness(struc
> >
> > static bool mem_cgroup_under_move(struct mem_cgroup *mem)
> > {
> > - struct mem_cgroup *from = mc.from;
> > - struct mem_cgroup *to = mc.to;
> > + struct mem_cgroup *from;
> > + struct mem_cgroup *to;
> > bool ret = false;
> > -
> > - if (from == mem || to == mem)
> > - return true;
> > -
> > - if (!from || !to || !mem->use_hierarchy)
> > - return false;
> > -
> > - rcu_read_lock();
> > - if (css_tryget(&from->css)) {
> > - ret = css_is_ancestor(&from->css, &mem->css);
> > - css_put(&from->css);
> > - }
> > - if (!ret && css_tryget(&to->css)) {
> > - ret = css_is_ancestor(&to->css, &mem->css);
> > + /*
> > + * Unlike task_move routines, we access mc.to, mc.from not under
> > + * mutual execution by cgroup_mutex. Here, we take spinlock instead.
> ^^^^^
> Typo should be exclusion
Sure.
>
> > + */
> > + spin_lock_irq(&mc.lock);
>
> Why do we use the _irq variant here?
>
Hmm. I'd like to add preemption_disable() or disable irq here. This spinlock
is held as
cgroup_mutex();
-> mc.lock
Then, I don't want to have a risk for preemption. But yes, logically, disabling irq
isn't necessary. I'll remove _irq() in the next.
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:[~2010-06-02 0:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 9:24 [RFC][1/3] memcg clean up try charge KAMEZAWA Hiroyuki
2010-06-01 9:27 ` [RFC][2/3] memcg safe operaton for checking a cgroup is under move accounts KAMEZAWA Hiroyuki
2010-06-01 9:29 ` [RFC][3/3] memcg swap accounts remove experimental KAMEZAWA Hiroyuki
2010-06-01 10:04 ` Balbir Singh
2010-06-01 13:24 ` Daisuke Nishimura
2010-06-01 11:25 ` [RFC][2/3] memcg safe operaton for checking a cgroup is under move accounts Balbir Singh
2010-06-02 0:37 ` KAMEZAWA Hiroyuki [this message]
2010-06-01 11:36 ` [RFC][1/3] memcg clean up try charge Balbir Singh
2010-06-02 0:42 ` KAMEZAWA Hiroyuki
2010-06-01 14:19 ` Daisuke Nishimura
2010-06-02 0:45 ` KAMEZAWA Hiroyuki
2010-06-02 1:39 ` 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=20100602093732.1026eaf3.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-mm@kvack.org \
--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