From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: balbir@linux.vnet.ibm.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
nishimura@mxp.nes.nec.co.jp, menage@google.com
Subject: Re: [RFC][PATCH 1/6] memcg: free all at rmdir
Date: Thu, 13 Nov 2008 11:30:35 +0900 [thread overview]
Message-ID: <20081113113035.844e8756.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <491B802B.2060401@linux.vnet.ibm.com>
On Thu, 13 Nov 2008 06:47:31 +0530
Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> > btw, mem_cgroup_force_empty_list() uses PageLRU() outside ->lru_lock.
> > That's racy, although afaict this race will only cause an accounting
> > error.
> >
> > Or maybe not. What happens if
> > __mem_cgroup_uncharge_common()->__mem_cgroup_remove_list() is passed a
> > page which isn't on an LRU any more? boom?
> >
>
> IIRC, Kamezawa has been working on redoing force_empty interface. We are
> reworking its internals as well.
>
PageLRU() is not used in account_move() version (in mmotm queue)
patches/memcg-move-all-acccounts-to-parent-at-rmdir.patch removes that.
We're now testing patch [6/6] which does
1. remove per-memcg-lru-lock
2. use zone->lru_lock instead of that.
Then, maintenance of this memcontrol.c will be much easier.
After patch [6/6]. account_move does
isolate_page(page);
move to other cgroup
putback_lru_page(page);
as other usual routine does.
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>
next prev parent reply other threads:[~2008-11-13 2:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 3:26 [RFC][PATCH 0/6] memcg updates (12/Nov/2008) KAMEZAWA Hiroyuki
2008-11-12 3:26 ` [RFC][PATCH 1/6] memcg: free all at rmdir KAMEZAWA Hiroyuki
2008-11-12 6:07 ` KAMEZAWA Hiroyuki
2008-11-13 0:07 ` Andrew Morton
2008-11-13 0:23 ` Balbir Singh
2008-11-13 0:46 ` Andrew Morton
2008-11-13 0:48 ` Balbir Singh
2008-11-13 1:04 ` Andrew Morton
2008-11-13 1:17 ` Balbir Singh
2008-11-13 2:30 ` KAMEZAWA Hiroyuki [this message]
2008-11-13 1:13 ` KAMEZAWA Hiroyuki
2008-11-13 1:20 ` Balbir Singh
2008-11-13 1:27 ` KAMEZAWA Hiroyuki
2008-11-13 2:49 ` KAMEZAWA Hiroyuki
2008-11-13 3:14 ` Balbir Singh
2008-11-13 3:22 ` KAMEZAWA Hiroyuki
2008-11-13 3:27 ` Balbir Singh
2008-11-13 3:38 ` KAMEZAWA Hiroyuki
2008-11-12 3:27 ` [RFC][PATCH 2/6] memcg: account swapcache KAMEZAWA Hiroyuki
2008-11-12 3:28 ` [RFC][PATCH 3/6] memcg: mem+swap controller kconfig KAMEZAWA Hiroyuki
2008-11-12 3:29 ` [RFC][PATCH 4/6] memcg: swap cgroup for remembering account KAMEZAWA Hiroyuki
2008-11-12 4:17 ` Daisuke Nishimura
2008-11-12 4:22 ` KAMEZAWA Hiroyuki
2008-11-12 3:30 ` [RFC][PATCH 5/6] memcg: mem+swap controller KAMEZAWA Hiroyuki
2008-11-12 3:32 ` [RFC][PATCH 6/6] memcg: synchronized LRU KAMEZAWA Hiroyuki
2008-11-12 3:33 ` [RFC][PATCH 0/6] memcg updates (12/Nov/2008) KAMEZAWA Hiroyuki
2008-11-12 4:00 ` Balbir Singh
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=20081113113035.844e8756.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=menage@google.com \
--cc=nishimura@mxp.nes.nec.co.jp \
/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