linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Greg Thelen <gthelen@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	containers@lists.osdl.org, Andrea Righi <arighi@develer.com>,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
	Minchan Kim <minchan.kim@gmail.com>,
	Ciju Rajan K <ciju@linux.vnet.ibm.com>,
	David Rientjes <rientjes@google.com>
Subject: Re: [PATCH v2 04/11] memcg: disable softirq in lock_page_cgroup()
Date: Mon, 18 Oct 2010 09:44:37 +0900	[thread overview]
Message-ID: <20101018094437.e12aae49.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <1287177279-30876-5-git-send-email-gthelen@google.com>

On Fri, 15 Oct 2010 14:14:32 -0700
Greg Thelen <gthelen@google.com> wrote:

> If pages are being migrated from a memcg, then updates to that
> memcg's page statistics are protected by grabbing a bit spin lock
> using lock_page_cgroup().  In an upcoming commit memcg dirty page
> accounting will be updating memcg page accounting (specifically:
> num writeback pages) from softirq.  Avoid a deadlocking nested
> spin lock attempt by disabling softirq on the local processor
> when grabbing the page_cgroup bit_spin_lock in lock_page_cgroup().
> This avoids the following deadlock:
> statistic
>       CPU 0             CPU 1
>                     inc_file_mapped
>                     rcu_read_lock
>   start move
>   synchronize_rcu
>                     lock_page_cgroup
>                       softirq
>                       test_clear_page_writeback
>                       mem_cgroup_dec_page_stat(NR_WRITEBACK)
>                       rcu_read_lock
>                       lock_page_cgroup   /* deadlock */
>                       unlock_page_cgroup
>                       rcu_read_unlock
>                     unlock_page_cgroup
>                     rcu_read_unlock
> 
> By disabling softirq in lock_page_cgroup, nested calls are avoided.
> The softirq would be delayed until after inc_file_mapped enables
> softirq when calling unlock_page_cgroup().
> 
> The normal, fast path, of memcg page stat updates typically
> does not need to call lock_page_cgroup(), so this change does
> not affect the performance of the common case page accounting.
> 
> Signed-off-by: Andrea Righi <arighi@develer.com>
> Signed-off-by: Greg Thelen <gthelen@google.com>

I have a patch for this problem.
So, could you reorder patch as

	1,2,3,5,6,7,8,9,10,11 

I'll post an add-on patch."12"

move_charge performance improbement patches will be posted later.

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>

  parent reply	other threads:[~2010-10-18  0:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-15 21:14 [PATCH v2 00/11] memcg: per cgroup dirty page accounting Greg Thelen
2010-10-15 21:14 ` [PATCH v2 01/11] memcg: add page_cgroup flags for dirty page tracking Greg Thelen
2010-10-15 21:14 ` [PATCH v2 02/11] memcg: document cgroup dirty memory interfaces Greg Thelen
2010-10-18  0:40   ` KAMEZAWA Hiroyuki
2010-10-15 21:14 ` [PATCH v2 03/11] memcg: create extensible page stat update routines Greg Thelen
2010-10-18  0:42   ` KAMEZAWA Hiroyuki
2010-10-15 21:14 ` [PATCH v2 04/11] memcg: disable softirq in lock_page_cgroup() Greg Thelen
2010-10-17  5:56   ` Minchan Kim
2010-10-18  0:44   ` KAMEZAWA Hiroyuki [this message]
2010-10-15 21:14 ` [PATCH v2 05/11] memcg: add dirty page accounting infrastructure Greg Thelen
2010-10-18  0:45   ` KAMEZAWA Hiroyuki
2010-10-15 21:14 ` [PATCH v2 06/11] memcg: add kernel calls for memcg dirty page stats Greg Thelen
2010-10-15 21:14 ` [PATCH v2 07/11] memcg: add dirty limits to mem_cgroup Greg Thelen
2010-10-18  0:49   ` KAMEZAWA Hiroyuki
2010-10-15 21:14 ` [PATCH v2 08/11] memcg: CPU hotplug lockdep warning fix Greg Thelen
2010-10-18  0:52   ` KAMEZAWA Hiroyuki
2010-10-15 21:14 ` [PATCH v2 09/11] memcg: add cgroupfs interface to memcg dirty limits Greg Thelen
2010-10-18  0:53   ` KAMEZAWA Hiroyuki
2010-10-15 21:14 ` [PATCH v2 10/11] writeback: make determine_dirtyable_memory() static Greg Thelen
2010-10-18  0:54   ` KAMEZAWA Hiroyuki
2010-10-15 21:14 ` [PATCH v2 11/11] memcg: check memcg dirty limits in page writeback Greg Thelen

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=20101018094437.e12aae49.kamezawa.hiroyu@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=arighi@develer.com \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=ciju@linux.vnet.ibm.com \
    --cc=containers@lists.osdl.org \
    --cc=gthelen@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan.kim@gmail.com \
    --cc=nishimura@mxp.nes.nec.co.jp \
    --cc=rientjes@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox