Date: Wed, 23 Mar 2005 15:20:55 -0800
From: Andrew Morton <akpm@osdl.org>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: cmm@us.ibm.com, andrea@suse.de, linux-kernel@vger.kernel.org,
       ext2-devel@lists.sourceforge.net
Subject: Re: OOM problems on 2.6.12-rc1 with many fsx tests
Message-Id: <20050323152055.6fc8c198.akpm@osdl.org>
In-Reply-To: <17250000.1111619602@flay>
References: <20050315204413.GF20253@csail.mit.edu>
	<20050316003134.GY7699@opteron.random>
	<20050316040435.39533675.akpm@osdl.org>
	<20050316183701.GB21597@opteron.random>
	<1111607584.5786.55.camel@localhost.localdomain>
	<20050323144953.288a5baf.akpm@osdl.org>
	<17250000.1111619602@flay>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1209
Lines: 29

"Martin J. Bligh" <mbligh@aracnet.com> wrote:
>
> > It would be interesting if you could run the same test on 2.6.11.  
> 
> One thing I'm finding is that it's hard to backtrace who has each page
> in this sort of situation. My plan is to write a debug patch to walk
> mem_map and dump out some info on each page. I would appreciate ideas
> on what info would be useful here. Some things are fairly obvious, like
> we want to know if it's anon / mapped into address space (& which),
> whether it's slab / buffers / pagecache etc ... any other suggestions
> you have would be much appreciated.

You could use

	page-owner-tracking-leak-detector.patch
	make-page_owner-handle-non-contiguous-page-ranges.patch
	add-gfp_mask-to-page-owner.patch

which sticks an 8-slot stack backtrace into each page, recording who
allocated it.

But that's probably not very interesting info for pagecache pages.

Nothing beats poking around in a dead machine's guts with kgdb though.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/