[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100413135718.GA4493@redhat.com>
Date: Tue, 13 Apr 2010 09:57:19 -0400
From: Vivek Goyal <vgoyal@...hat.com>
To: KAMEZAWA Hiroyuki <amezawa.hiroyu@...fujitsu.com>
Cc: Randy Dunlap <randy.dunlap@...cle.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"nishimura@....nes.nec.co.jp" <nishimura@....nes.nec.co.jp>,
"balbir@...ux.vnet.ibm.com" <balbir@...ux.vnet.ibm.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] memcg: update documentation v5
On Tue, Apr 13, 2010 at 01:45:53PM +0900, KAMEZAWA Hiroyuki wrote:
[..]
> -2. Locking
> +2.6 Locking
>
> -The memory controller uses the following hierarchy
> + lock_page_cgroup()/unlock_page_cgroup() should not be called under
> + mapping->tree_lock.
>
Because I never understood very well, I will ask. Why lock_page_cgroup()
should not be called under mapping->tree_lock?
Thanks
Vivek
--
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