From: David Rientjes <rientjes@google.com>
To: Christoph Lameter <cl@linux.com>
Cc: Matt Mackall <mpm@selenic.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
linux-mm@kvack.org
Subject: Re: [patch] slob: fix gfp flags for order-0 page allocations
Date: Tue, 24 Aug 2010 13:24:17 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1008241323400.21242@chino.kir.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1008241036250.344@router.home>
On Tue, 24 Aug 2010, Christoph Lameter wrote:
> > kmalloc-32 1113344 1113344 32 128 1 : tunables 0 0
> > 0 : slabdata 8698 8698 0
> >
> > That's /proc/slabinfo on my laptop with SLUB. It looks like my last
> > reboot popped me back to 2.6.33 so it may also be old news, but I
> > couldn't spot any reports with Google.
>
> Boot with "slub_debug" as a kernel parameter
>
> and then do a
>
> cat /sys/kernel/slab/kmalloc-32/alloc_calls
>
> to find the caller allocating the objets.
>
I'd suspect this was anon_vma, and enabling CONFIG_DEBUG_KMEMLEAK would
probably reveal exactly where it's getting leaked.
--
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:[~2010-08-24 20:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-22 23:16 David Rientjes
2010-08-23 0:51 ` Christoph Lameter
2010-08-24 4:26 ` Matt Mackall
2010-08-24 4:36 ` David Rientjes
2010-08-24 15:20 ` Matt Mackall
2010-08-24 15:37 ` Christoph Lameter
2010-08-24 20:24 ` David Rientjes [this message]
2010-08-24 17:44 ` Pekka Enberg
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=alpine.DEB.2.00.1008241323400.21242@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=cl@linux.com \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=penberg@cs.helsinki.fi \
/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