[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20081202161837.1D04.KOSAKI.MOTOHIRO@jp.fujitsu.com>
Date: Tue, 2 Dec 2008 16:19:20 +0900 (JST)
From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc: kosaki.motohiro@...fujitsu.com,
LKML <linux-kernel@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>,
Balbir Singh <balbir@...ux.vnet.ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 1/2] memcg: mem_cgroup->prev_priority protected by lock.
> On Tue, 2 Dec 2008 16:11:07 +0900 (JST)
> KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> wrote:
>
> >
> > Currently, mem_cgroup doesn't have own lock and almost its member doesn't need.
> > (e.g. info is protected by zone lock, stat is per cpu variable)
> >
> > However, there is one explict exception. mem_cgroup->prev_priorit need lock,
> > but doesn't protect.
> > Luckly, this is NOT bug because prev_priority isn't used for current reclaim code.
> >
> > However, we plan to use prev_priority future again.
> > Therefore, fixing is better.
> >
> >
> > In addision, we plan to reuse this lock for another member.
> > Then "misc_lock" name is better than "prev_priority_lock".
> >
> please use better name...reclaim_param_lock or some ?
good idea :)
Will fix.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists