From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: balbir@linux.vnet.ibm.com, MinChan Kim <minchan.kim@gmail.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
linux-mm <linux-mm@kvack.org>, Rik van Riel <riel@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Race condition between putback_lru_page and mem_cgroup_move_list
Date: Thu, 07 Aug 2008 07:27:14 -0400 [thread overview]
Message-ID: <1218108434.6086.29.camel@lts-notebook> (raw)
In-Reply-To: <20080807185203.A8C2.KOSAKI.MOTOHIRO@jp.fujitsu.com>
On Thu, 2008-08-07 at 20:00 +0900, KOSAKI Motohiro wrote:
> Hi
>
> > If you mean the "active/inactive list transition" in
> > shrink_[in]active_list(), these are already batched under zone lru_lock
> > with batch size determined by the 'release pages' pvec. So, I think
> > we're OK here.
>
> No.
>
> AFAIK shrink_inactive_list batched zone->lru_lock,
> but it doesn't batched mz->lru_lock.
>
> then, spin_lock_irqsave is freqently called.
Ah, I see what you mean. Yes, the mem cgroup zone lru_lock will be
cycled frequently as each back of pages is put back during reclaim. So,
you'd like to eliminate the mz lru_lock, move the mem cgroup zone info
under the corresponding zone lru_lock and move the page between memcg
lists atomically with adding to global lru lists?
Lee
--
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:[~2008-08-07 11:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 14:36 MinChan Kim
2008-08-04 15:31 ` Lee Schermerhorn
2008-08-04 16:37 ` KOSAKI Motohiro
2008-08-04 17:52 ` Balbir Singh
2008-08-04 23:52 ` MinChan Kim
2008-08-05 6:20 ` KOSAKI Motohiro
2008-08-05 10:46 ` Balbir Singh
2008-08-05 11:19 ` KOSAKI Motohiro
2008-08-05 11:38 ` KOSAKI Motohiro
2008-08-06 16:53 ` Lee Schermerhorn
2008-08-07 11:00 ` KOSAKI Motohiro
2008-08-07 11:27 ` Lee Schermerhorn [this message]
2008-08-07 12:42 ` Balbir Singh
2008-08-05 3:49 ` kamezawa.hiroyu
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=1218108434.6086.29.camel@lts-notebook \
--to=lee.schermerhorn@hp.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=riel@redhat.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