From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Tvrtko Ursulin <tvrtko.ursulin@sophos.com>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: 2.6.33.2 kmalloc-8 slab leaks ~512 objects per second
Date: Wed, 12 May 2010 16:00:51 +0300 [thread overview]
Message-ID: <g2i84144f021005120600wa8eb0409k13f67f49c519509@mail.gmail.com> (raw)
In-Reply-To: <201005121121.49135.tvrtko.ursulin@sophos.com>
Hi Tvrtko,
On Wed, May 12, 2010 at 1:21 PM, Tvrtko Ursulin
<tvrtko.ursulin@sophos.com> wrote:
> As the subject says, is this a know issue? I have been tracking the growth at
> one second intervals and it looks like this:
>
> 512 (67716608) Slab: 606744 kB
> 512 (67717120) Slab: 606752 kB
> 512 (67717632) Slab: 606756 kB
> 0 (67718144) Slab: 606756 kB
> 512 (67718144) Slab: 606760 kB
> 1024 (67718656) Slab: 606768 kB
> 512 (67719680) Slab: 606772 kB
> 512 (67720192) Slab: 606776 kB
> 0 (67720704) Slab: 606776 kB
> 512 (67720704) Slab: 606780 kB
>
> First fiels is the diff in numobj, in parentheses is actual numobj and last is
> the total slab size from /proc/meminfo.
>
> kmalloc-8 68044800 68044800 8 512 1 : tunables 0 0 0
> : slabdata 132900 132900 0
>
> dm-io slab also seems large, don't know... :
> dm_io 75924 147288 40 102 1 : tunables 0 0 0 :
> slabdata 1444 1444 0
>
> Some other info about the system/kernel is attached.
[snip]
You might want to try out the built-in kernel memory leak detector.
See Documentation/kmemleak.txt for details how to enable it and use
it.
Pekka
next prev parent reply other threads:[~2010-05-12 13:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 10:21 Tvrtko Ursulin
2010-05-12 13:00 ` Pekka Enberg [this message]
2010-05-12 13:04 ` Tvrtko Ursulin
2010-05-13 12:29 ` Catalin Marinas
2010-05-13 12:39 ` Tvrtko Ursulin
2010-05-26 9:21 ` David Rientjes
2010-05-26 16:22 ` Tvrtko Ursulin
[not found] <11758_1273660249_4BEA8359_11758_1675_1_201005121121.49135.tvrtko.ursulin@sophos.com>
2010-05-12 10:38 ` Tvrtko Ursulin
2010-05-12 10:50 ` Tvrtko Ursulin
2010-05-12 13:29 ` Jerome Glisse
2010-05-12 13:37 ` Tvrtko Ursulin
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=g2i84144f021005120600wa8eb0409k13f67f49c519509@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tvrtko.ursulin@sophos.com \
/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
all inboxes | Powered by JetHome®