From: Andrew Morton <akpm@linux-foundation.org>
To: Vincent Whitchurch <vincent.whitchurch@axis.com>
Cc: catalin.marinas@arm.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Vincent Whitchurch <rabinv@axis.com>
Subject: Re: [PATCH 2/2] scripts: add kmemleak2pprof.py for slab usage analysis
Date: Tue, 28 Aug 2018 16:28:04 -0700 [thread overview]
Message-ID: <20180828162804.4ee225124cbde3f39f53fd80@linux-foundation.org> (raw)
In-Reply-To: <20180828103914.30434-2-vincent.whitchurch@axis.com>
On Tue, 28 Aug 2018 12:39:14 +0200 Vincent Whitchurch <vincent.whitchurch@axis.com> wrote:
> Add a script which converts /sys/kernel/debug/kmemleak_all to the pprof
> format, which can be used for analysing memory usage. See
> https://github.com/google/pprof.
Why is this better than /proc/slabinfo?
> $ ./kmemleak2pprof.py kmemleak_all
> $ pprof -text -ignore free_area_init_node -compact_labels -nodecount 10 prof
Are we missing an argument here? s/prof/kmemleak_all/?
> Showing nodes accounting for 4.85MB, 34.05% of 14.23MB total
> Dropped 3989 nodes (cum <= 0.07MB)
> Showing top 10 nodes out of 190
> flat flat% sum% cum cum%
> 1.39MB 9.78% 9.78% 1.61MB 11.29% new_inode_pseudo+0x8/0x4c
> 0.75MB 5.27% 15.04% 0.75MB 5.27% alloc_large_system_hash+0x19c/0x2b8
> 0.73MB 5.12% 20.17% 0.86MB 6.07% kernfs_new_node+0x30/0x50
> 0.66MB 4.62% 24.79% 0.66MB 4.62% __vmalloc_node.constprop.9+0x48/0x50
> 0.61MB 4.28% 29.06% 0.61MB 4.28% d_alloc+0x10/0x78
> 0.22MB 1.52% 30.58% 0.22MB 1.52% alloc_inode+0x1c/0xa4
> 0.18MB 1.28% 31.86% 0.20MB 1.42% _do_fork+0xb0/0x41c
> 0.13MB 0.88% 32.74% 0.13MB 0.88% early_trace_init+0x16c/0x374
> 0.09MB 0.66% 33.40% 0.17MB 1.17% inet_init+0x128/0x24c
> 0.09MB 0.65% 34.05% 0.09MB 0.65% __kernfs_new_node+0x34/0x1a8
next prev parent reply other threads:[~2018-08-28 23:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 10:39 [PATCH 1/2] kmemleak: dump all objects for slab usage analysis Vincent Whitchurch
2018-08-28 10:39 ` [PATCH 2/2] scripts: add kmemleak2pprof.py " Vincent Whitchurch
2018-08-28 23:28 ` Andrew Morton [this message]
2018-08-30 7:29 ` Vincent Whitchurch
2018-08-31 0:21 ` Andrew Morton
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=20180828162804.4ee225124cbde3f39f53fd80@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rabinv@axis.com \
--cc=vincent.whitchurch@axis.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;
as well as URLs for NNTP newsgroup(s).