All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: KAMEZAWA Hiroyuki <amezawa.hiroyu@jp.fujitsu.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
	"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] memcg: update documentation v5
Date: Tue, 13 Apr 2010 09:57:19 -0400	[thread overview]
Message-ID: <20100413135718.GA4493@redhat.com> (raw)
In-Reply-To: <20100413134553.7e2c4d3d.kamezawa.hiroyu@jp.fujitsu.com>

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

WARNING: multiple messages have this Message-ID (diff)
From: Vivek Goyal <vgoyal@redhat.com>
To: KAMEZAWA Hiroyuki <amezawa.hiroyu@jp.fujitsu.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
	"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] memcg: update documentation v5
Date: Tue, 13 Apr 2010 09:57:19 -0400	[thread overview]
Message-ID: <20100413135718.GA4493@redhat.com> (raw)
In-Reply-To: <20100413134553.7e2c4d3d.kamezawa.hiroyu@jp.fujitsu.com>

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, 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>

  parent reply	other threads:[~2010-04-13 13:57 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08  5:58 [PATCH] memcg: update documentation v3 KAMEZAWA Hiroyuki
2010-04-08  5:58 ` KAMEZAWA Hiroyuki
2010-04-08 17:32 ` Randy Dunlap
2010-04-08 17:32   ` Randy Dunlap
2010-04-08 23:50   ` KAMEZAWA Hiroyuki
2010-04-08 23:50     ` KAMEZAWA Hiroyuki
2010-04-09  1:26 ` Daisuke Nishimura
2010-04-09  1:26   ` Daisuke Nishimura
2010-04-09  1:45   ` KAMEZAWA Hiroyuki
2010-04-09  1:45     ` KAMEZAWA Hiroyuki
2010-04-09  2:11     ` Daisuke Nishimura
2010-04-09  2:11       ` Daisuke Nishimura
2010-04-09  3:01       ` KAMEZAWA Hiroyuki
2010-04-09  3:01         ` KAMEZAWA Hiroyuki
2010-04-09  4:45 ` [PATCH] memcg: update documentation v4 KAMEZAWA Hiroyuki
2010-04-09  4:45   ` KAMEZAWA Hiroyuki
2010-04-09  5:50   ` Daisuke Nishimura
2010-04-09  5:50     ` Daisuke Nishimura
2010-04-09 17:04   ` Randy Dunlap
2010-04-09 17:04     ` Randy Dunlap
2010-04-13  4:45     ` [PATCH] memcg: update documentation v5 KAMEZAWA Hiroyuki
2010-04-13  4:45       ` KAMEZAWA Hiroyuki
2010-04-13  6:04       ` Balbir Singh
2010-04-13  6:04         ` Balbir Singh
2010-04-13  6:20         ` KAMEZAWA Hiroyuki
2010-04-13  6:20           ` KAMEZAWA Hiroyuki
2010-04-13  6:48           ` Balbir Singh
2010-04-13  6:48             ` Balbir Singh
2010-04-13  6:58             ` [PATCH] memcg: update documentation v6 KAMEZAWA Hiroyuki
2010-04-13  6:58               ` KAMEZAWA Hiroyuki
2010-04-13 15:54               ` Randy Dunlap
2010-04-13 15:54                 ` Randy Dunlap
2010-04-14  1:22                 ` [PATCH] memcg: update documentation v7 KAMEZAWA Hiroyuki
2010-04-14  1:22                   ` KAMEZAWA Hiroyuki
2010-04-14 18:11                   ` Randy Dunlap
2010-04-14 18:11                     ` Randy Dunlap
2010-04-15  0:34                     ` [PATCH] memcg: update documentation v8 KAMEZAWA Hiroyuki
2010-04-15  0:34                       ` KAMEZAWA Hiroyuki
2010-04-15 15:48                       ` Randy Dunlap
2010-04-15 15:48                         ` Randy Dunlap
2010-04-13 13:57       ` Vivek Goyal [this message]
2010-04-13 13:57         ` [PATCH] memcg: update documentation v5 Vivek Goyal
2010-04-13 14:03         ` Vivek Goyal
2010-04-13 14:03           ` Vivek Goyal
2010-04-13 15:08           ` Balbir Singh
2010-04-13 15:08             ` Balbir Singh
2010-04-13 15:16             ` Vivek Goyal
2010-04-13 15:16               ` Vivek Goyal

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=20100413135718.GA4493@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=amezawa.hiroyu@jp.fujitsu.com \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nishimura@mxp.nes.nec.co.jp \
    --cc=randy.dunlap@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.