[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090515084716.544930d9.kamezawa.hiroyu@jp.fujitsu.com>
Date: Fri, 15 May 2009 08:47:16 +0900
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc: balbir@...ux.vnet.ibm.com,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"nishimura@....nes.nec.co.jp" <nishimura@....nes.nec.co.jp>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
mingo@...e.hu,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/3] fix stale swap cache account leak in memcg v7
On Wed, 13 May 2009 09:31:27 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> wrote:
> On Tue, 12 May 2009 15:21:58 +0530
> Balbir Singh <balbir@...ux.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.
Hm, I didn't think this problem took 2 months to be fixed ;(
-Kame
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists