From: Li Zefan <lizf@cn.fujitsu.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: [PATCH 0/5] perf kmem: Add more functions and show more statistics
Date: Tue, 24 Nov 2009 13:25:24 +0800 [thread overview]
Message-ID: <4B0B6E44.6090106@cn.fujitsu.com> (raw)
List of new things:
- Add option "--raw-ip", to print raw ip instead of symbols.
- Sort the output by fragmentation by default, and support
multi keys.
- Collect and show cross node allocation stats.
- Collect and show alloc/free ping-pong stats.
- And help file.
---
tools/perf/Documentation/perf-kmem.txt | 44 ++++
tools/perf/builtin-kmem.c | 353 ++++++++++++++++++++++++++------
tools/perf/command-list.txt | 1 +
3 files changed, 331 insertions(+), 67 deletions(-)
Pekka, do you think we can remove kmemtrace now?
With kmem trace events, low-level analyzing can be done using
ftrace, and high-level analyzing can be done using perf-kmem.
And chance is, more people may use and improve perf-kmem, and it
will be well-maintained within the perf infrastructure. On the
other hand, I guess few people use and contribute to kmemtrace-user.
BTW, seems kmemtrace-user doesn't work with ftrace. I got setfault:
# ./kmemtraced
Copying /proc/kallsyms...
Logging... Press Control-C to stop.
^CSegmentation fault
--
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 reply other threads:[~2009-11-24 5:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 5:25 Li Zefan [this message]
2009-11-24 5:25 ` [PATCH 1/5] perf kmem: Add new option to show raw ip Li Zefan
2009-11-24 16:54 ` [tip:perf/core] " tip-bot for Li Zefan
2009-11-24 5:26 ` [PATCH 2/5] perf kmem: Default to sort by fragmentation Li Zefan
2009-11-24 16:55 ` [tip:perf/core] " tip-bot for Li Zefan
2009-11-24 5:26 ` [PATCH 3/5] perf kmem: Collect cross node allocation statistics Li Zefan
2009-11-24 16:55 ` [tip:perf/core] " tip-bot for Li Zefan
2009-11-24 5:26 ` [PATCH 4/5] perf kmem: Measure kmalloc/kfree CPU ping-pong call-sites Li Zefan
2009-11-24 16:55 ` [tip:perf/core] " tip-bot for Li Zefan
2009-11-24 5:27 ` [PATCH 5/5] perf kmem: Add help file Li Zefan
2009-11-24 16:55 ` [tip:perf/core] " tip-bot for Li Zefan
2009-11-24 7:15 ` [PATCH 0/5] perf kmem: Add more functions and show more statistics Pekka Enberg
2009-11-24 7:34 ` Ingo Molnar
2009-11-24 7:45 ` Pekka Enberg
2009-11-24 7:47 ` Ingo Molnar
2009-11-24 8:04 ` Li Zefan
2009-11-24 8:34 ` Ingo Molnar
2009-11-24 14:57 ` Arjan van de Ven
2009-11-24 7:18 ` Pekka Enberg
2009-11-24 9:04 ` Ingo Molnar
2009-11-24 9:38 ` Li Zefan
2009-11-24 10:07 ` Ingo Molnar
2009-11-24 11:04 ` Li Zefan
2009-11-24 20:35 ` Ingo Molnar
2009-11-24 22:34 ` Ingo Molnar
2009-11-24 18:49 ` Frederic Weisbecker
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=4B0B6E44.6090106@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=eduard.munteanu@linux360.ro \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=peterz@infradead.org \
/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