Messages in this thread | | | Date | Tue, 22 Jan 2013 15:41:19 +0200 | Subject | Re: [RFC/PATCH] scripts/tracing: Add trace_analyze.py tool | From | Pekka Enberg <> |
| |
(Adding acme to CC.)
On Tue, Jan 22, 2013 at 11:46 AM, Ezequiel Garcia <ezequiel.garcia@free-electrons.com> wrote: > From: Ezequiel Garcia <elezegarcia@gmail.com> > > The purpose of trace_analyze.py tool is to perform static > and dynamic memory analysis using a kmem ftrace > log file and a built kernel tree. > > This script and related work has been done on the CEWG/2012 project: > "Kernel dynamic memory allocation tracking and reduction" > (More info here [1]) > > It produces mainly two kinds of outputs: > * an account-like output, similar to the one given by Perf, example below. > * a ring-char output, examples here [2]. > > $ ./scripts/tracing/trace_analyze.py -k linux -f kmem.log --account-file account.txt > $ ./scripts/tracing/trace_analyze.py -k linux -f kmem.log -c account.txt > > This will produce an account file like this: > > current bytes allocated: 669696 > current bytes requested: 618823 > current wasted bytes: 50873 > number of allocs: 7649 > number of frees: 2563 > number of callers: 115 > > total waste net alloc/free caller > --------------------------------------------- > 299200 0 298928 1100/1 alloc_inode+0x4fL > 189824 0 140544 1483/385 __d_alloc+0x22L > 51904 0 47552 811/68 sysfs_new_dirent+0x4eL > [...] > > [1] http://elinux.org/Kernel_dynamic_memory_analysis > [2] http://elinux.org/Kernel_dynamic_memory_analysis#Current_dynamic_footprint > > Cc: Pekka Enberg <penberg@kernel.org> > Cc: Steven Rostedt <rostedt@goodmis.org> > Cc: Frederic Weisbecker <fweisbec@gmail.com> > Cc: Ingo Molnar <mingo@redhat.com> > Signed-off-by: Ezequiel Garcia <elezegarcia@gmail.com>
Looks really useful! Dunno if this makes most sense as a separate script or as an extension perf.
Pekka
| |