From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753088AbZKXF0H (ORCPT ); Tue, 24 Nov 2009 00:26:07 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751462AbZKXF0G (ORCPT ); Tue, 24 Nov 2009 00:26:06 -0500 Received: from cn.fujitsu.com ([222.73.24.84]:53211 "EHLO song.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1751555AbZKXF0A (ORCPT ); Tue, 24 Nov 2009 00:26:00 -0500 Message-ID: <4B0B6E44.6090106@cn.fujitsu.com> Date: Tue, 24 Nov 2009 13:25:24 +0800 From: Li Zefan User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Thunderbird/3.0b2 MIME-Version: 1.0 To: Ingo Molnar CC: Pekka Enberg , Eduard - Gabriel Munteanu , Peter Zijlstra , Frederic Weisbecker , LKML , "linux-mm@kvack.org" Subject: [PATCH 0/5] perf kmem: Add more functions and show more statistics Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail138.messagelabs.com (mail138.messagelabs.com [216.82.249.35]) by kanga.kvack.org (Postfix) with SMTP id 357986B006A for ; Tue, 24 Nov 2009 00:26:08 -0500 (EST) Message-ID: <4B0B6E44.6090106@cn.fujitsu.com> Date: Tue, 24 Nov 2009 13:25:24 +0800 From: Li Zefan MIME-Version: 1.0 Subject: [PATCH 0/5] perf kmem: Add more functions and show more statistics Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org To: Ingo Molnar Cc: Pekka Enberg , Eduard - Gabriel Munteanu , Peter Zijlstra , Frederic Weisbecker , LKML , "linux-mm@kvack.org" List-ID: 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: email@kvack.org