From: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: nishimura@mxp.nes.nec.co.jp, balbir@linux.vnet.ibm.com,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
mingo@elte.hu,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] fix stale swap cache account leak in memcg v7
Date: Fri, 15 May 2009 10:12:23 +0900 [thread overview]
Message-ID: <20090515101223.12d5a80f.nishimura@mxp.nes.nec.co.jp> (raw)
In-Reply-To: <20090515095445.9492fe13.kamezawa.hiroyu@jp.fujitsu.com>
On Fri, 15 May 2009 09:54:45 +0900, KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> On Fri, 15 May 2009 09:38:53 +0900
> Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
>
> > On Fri, 15 May 2009 08:47:16 +0900, KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> > > On Wed, 13 May 2009 09:31:27 +0900
> > > KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> > >
> > > > On Tue, 12 May 2009 15:21:58 +0530
> > > > Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> > > >
> > > > > > The patch set includes followng
> > > > > > [1/3] add mem_cgroup_is_activated() function. which tell us memcg is _really_ used.
> > > > > > [2/3] fix swap cache handling race by avoidng readahead.
> > > > > > [3/3] fix swap cache handling race by check swapcount again.
> > > > > >
> > > > > > Result is good under my test.
> > > > >
> > > > > What was the result (performance data impact) of disabling swap
> > > > > readahead? Otherwise, this looks the most reasonable set of patches
> > > > > for this problem.
> > > > >
> > > > I'll measure some and report it in the next post.
> > > >
> > > I confirmed there are cases which swapin readahead works very well....
> > >
> > > Nishimura-san, could you post a patch for fixing leak at writeback ? as [3/3]
> > > I'd like to fix readahead case...with some large patch.
> > >
> > Sure.
> > I'll rebase my patch onto [1-2/3] of your new patch and post it.
> >
> Ah, plz go ahead and don't wait for me. Mine is just under rough design now.
>
I see.
Thanks,
Daisuke Nishimura.
--
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>
prev parent reply other threads:[~2009-05-15 1:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 1:44 KAMEZAWA Hiroyuki
2009-05-12 1:45 ` [PATCH 1/3] add check for mem cgroup is activated KAMEZAWA Hiroyuki
2009-05-12 1:46 ` [PATCH 2/3] fix swap cache account leak at swapin-readahead KAMEZAWA Hiroyuki
2009-05-12 4:32 ` Daisuke Nishimura
2009-05-12 11:24 ` Johannes Weiner
2009-05-12 23:58 ` KAMEZAWA Hiroyuki
2009-05-13 11:18 ` Johannes Weiner
2009-05-13 18:03 ` Hugh Dickins
2009-05-14 0:05 ` KAMEZAWA Hiroyuki
2009-05-12 1:47 ` [PATCH 3/3] fix stale swap cache at writeback KAMEZAWA Hiroyuki
2009-05-12 5:06 ` [PATCH 4/3] memcg: call uncharge_swapcache outside of tree_lock (Re: [PATCH 0/3] fix stale swap cache account leak in memcg v7) Daisuke Nishimura
2009-05-12 7:09 ` KAMEZAWA Hiroyuki
2009-05-12 8:00 ` Daisuke Nishimura
2009-05-12 8:13 ` [PATCH][BUGFIX] memcg: fix for deadlock between lock_page_cgroup and mapping tree_lock KAMEZAWA Hiroyuki
2009-05-12 10:58 ` Daisuke Nishimura
2009-05-12 23:59 ` KAMEZAWA Hiroyuki
2009-05-13 0:28 ` Daisuke Nishimura
2009-05-13 0:32 ` KAMEZAWA Hiroyuki
2009-05-13 3:55 ` KAMEZAWA Hiroyuki
2009-05-13 4:11 ` nishimura
2009-05-12 9:51 ` [PATCH 0/3] fix stale swap cache account leak in memcg v7 Balbir Singh
2009-05-13 0:31 ` KAMEZAWA Hiroyuki
2009-05-14 23:47 ` KAMEZAWA Hiroyuki
2009-05-15 0:38 ` Daisuke Nishimura
2009-05-15 0:54 ` KAMEZAWA Hiroyuki
2009-05-15 1:12 ` Daisuke Nishimura [this message]
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=20090515101223.12d5a80f.nishimura@mxp.nes.nec.co.jp \
--to=nishimura@mxp.nes.nec.co.jp \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
/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