[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1202241342240.22880@chino.kir.corp.google.com>
Date: Fri, 24 Feb 2012 13:45:32 -0800 (PST)
From: David Rientjes <rientjes@...gle.com>
To: Josef Bacik <josef@...hat.com>
cc: Rafael Aquini <aquini@...hat.com>, linux-mm@...ck.org,
Randy Dunlap <rdunlap@...otime.net>,
Christoph Lameter <cl@...ux-foundation.org>,
Pekka Enberg <penberg@...nel.org>,
Matt Mackall <mpm@...enic.com>, Rik van Riel <riel@...hat.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] oom: add sysctl to enable slab memory dump
On Fri, 24 Feb 2012, Josef Bacik wrote:
> Um well yeah, I'm rewriting a chunk of btrfs which was rapantly leaking memory
> so the OOM just couldn't keep up with how much I was sucking down. This is
> strictly a developer is doing something stupid and needs help pointing out what
> it is sort of moment, not a day to day OOM.
>
If you're debugging new kernel code and you realize that excessive amount
of memory is being consumed so that nothing can even fork, you may want to
try cat /proc/slabinfo before you get into that condition the next time
around, although I already suspect that you know the cache you're leaking.
It doesn't mean we need to add hundreds of lines of code to the kernel.
Try kmemleak.
--
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