All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [RFC][PATCH 1/2] perf: Add 'perf kmem' tool
Date: Fri, 20 Nov 2009 16:20:57 +0800	[thread overview]
Message-ID: <4B065169.7080603@cn.fujitsu.com> (raw)
In-Reply-To: <20091120081440.GA19778@elte.hu>

>> TODO:
>> - show sym+offset in 'callsite' column
> 
> The way to print symbolic information for the 'callsite' column is to 
> fill in and walk the thread->DSO->symbol trees that all perf tools 
> maintain:
> 
> 	/* simplified, without error handling */
> 
> 	ip = event->ip.ip;
> 
> 	thread = threads__findnew(event->ip.pid);
> 
> 	map = thread__find_map(thread, ip);
> 
> 	ip = map->map_ip(map, ip); /* map absolute RIP into DSO-relative one */
> 
> 	sym = map__find_symbol(map, ip, symbol_filter);
> 
> then sym->name is the string that can be printed out. This works in a 
> symmetric way for both kernel-space and user-space symbols. (Call-chain 
> information can be captured and displayed too.)
> 
> ( 'Alloc Ptr' symbolization is harder, but it would be useful too i 
>   think, to map it back to the slab cache name. )
> 

Thanks.

I was lazy to figure it out by myself. ;)

>> - show cross node allocation stats
> 
> I checked and we appear to have all the right events for that - the node 
> ID is being traced consistently AFAICS.
> 

Actually kmemtrace-user shows this stats, but in a wrong way.
It doesn't map cpu_nr to node.

>> - collect more useful stats?
>> - ...
> 
> Pekka, Eduard and the other slab hackers might have ideas about what 
> other stats they generally like to see to judge the health of a workload 
> (or system).
> 
> If this iteration looks good to the slab folks then i can apply it as-is 
> and we can do the other changes relative to that. It looks good to me as 
> a first step, and it's functional already.
> 

Thanks!


WARNING: multiple messages have this Message-ID (diff)
From: Li Zefan <lizf@cn.fujitsu.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [RFC][PATCH 1/2] perf: Add 'perf kmem' tool
Date: Fri, 20 Nov 2009 16:20:57 +0800	[thread overview]
Message-ID: <4B065169.7080603@cn.fujitsu.com> (raw)
In-Reply-To: <20091120081440.GA19778@elte.hu>

>> TODO:
>> - show sym+offset in 'callsite' column
> 
> The way to print symbolic information for the 'callsite' column is to 
> fill in and walk the thread->DSO->symbol trees that all perf tools 
> maintain:
> 
> 	/* simplified, without error handling */
> 
> 	ip = event->ip.ip;
> 
> 	thread = threads__findnew(event->ip.pid);
> 
> 	map = thread__find_map(thread, ip);
> 
> 	ip = map->map_ip(map, ip); /* map absolute RIP into DSO-relative one */
> 
> 	sym = map__find_symbol(map, ip, symbol_filter);
> 
> then sym->name is the string that can be printed out. This works in a 
> symmetric way for both kernel-space and user-space symbols. (Call-chain 
> information can be captured and displayed too.)
> 
> ( 'Alloc Ptr' symbolization is harder, but it would be useful too i 
>   think, to map it back to the slab cache name. )
> 

Thanks.

I was lazy to figure it out by myself. ;)

>> - show cross node allocation stats
> 
> I checked and we appear to have all the right events for that - the node 
> ID is being traced consistently AFAICS.
> 

Actually kmemtrace-user shows this stats, but in a wrong way.
It doesn't map cpu_nr to node.

>> - collect more useful stats?
>> - ...
> 
> Pekka, Eduard and the other slab hackers might have ideas about what 
> other stats they generally like to see to judge the health of a workload 
> (or system).
> 
> If this iteration looks good to the slab folks then i can apply it as-is 
> and we can do the other changes relative to that. It looks good to me as 
> a first step, and it's functional already.
> 

Thanks!

--
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>

  parent reply	other threads:[~2009-11-20  8:21 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-20  7:53 [RFC][PATCH 1/2] perf: Add 'perf kmem' tool Li Zefan
2009-11-20  7:53 ` Li Zefan
2009-11-20  7:53 ` [PATCH 2/2] tracing: Remove kmemtrace tracer Li Zefan
2009-11-20  7:53   ` Li Zefan
2009-11-20  8:20   ` Pekka Enberg
2009-11-20  8:20     ` Pekka Enberg
2009-11-20  8:24     ` Li Zefan
2009-11-20  8:24       ` Li Zefan
2009-11-20  8:27       ` Pekka Enberg
2009-11-20  8:27         ` Pekka Enberg
2009-11-20  8:31         ` Li Zefan
2009-11-20  8:31           ` Li Zefan
2009-11-20  8:14 ` [RFC][PATCH 1/2] perf: Add 'perf kmem' tool Ingo Molnar
2009-11-20  8:14   ` Ingo Molnar
2009-11-20  8:19   ` Pekka Enberg
2009-11-20  8:19     ` Pekka Enberg
2009-11-20  8:30     ` Ingo Molnar
2009-11-20  8:30       ` Ingo Molnar
2009-11-20  8:47       ` Pekka Enberg
2009-11-20  8:47         ` Pekka Enberg
2009-11-20  8:53         ` Li Zefan
2009-11-20  8:53           ` Li Zefan
2009-11-20  9:03           ` Ingo Molnar
2009-11-20  9:03             ` Ingo Molnar
2009-11-20  9:14             ` Li Zefan
2009-11-20  9:14               ` Li Zefan
2009-11-20 14:42             ` Arnaldo Carvalho de Melo
2009-11-20 14:42               ` Arnaldo Carvalho de Melo
2009-11-20 16:41               ` Ingo Molnar
2009-11-20 16:41                 ` Ingo Molnar
2009-11-20 17:52                 ` Arnaldo Carvalho de Melo
2009-11-20 17:52                   ` Arnaldo Carvalho de Melo
2009-11-23  6:51                   ` Ingo Molnar
2009-11-23  6:51                     ` Ingo Molnar
2009-11-23  7:22                     ` Peter Zijlstra
2009-11-23  7:22                       ` Peter Zijlstra
2009-11-23  7:33                       ` Ingo Molnar
2009-11-23  7:33                         ` Ingo Molnar
2009-11-23 14:37                       ` Arnaldo Carvalho de Melo
2009-11-23 14:37                         ` Arnaldo Carvalho de Melo
2009-11-23 14:32                     ` Arnaldo Carvalho de Melo
2009-11-23 14:32                       ` Arnaldo Carvalho de Melo
2009-11-20  9:01         ` Ingo Molnar
2009-11-20  9:01           ` Ingo Molnar
2009-11-20  9:15           ` Pekka Enberg
2009-11-20  9:15             ` Pekka Enberg
2009-11-20 10:13             ` Ingo Molnar
2009-11-20 10:13               ` Ingo Molnar
2009-11-20 10:31               ` Pekka Enberg
2009-11-20 10:31                 ` Pekka Enberg
2009-11-20 10:49                 ` Ingo Molnar
2009-11-20 10:49                   ` Ingo Molnar
2009-11-23 14:46                   ` Steven Rostedt
2009-11-23 14:46                     ` Steven Rostedt
2009-11-23 17:53                     ` Ingo Molnar
2009-11-23 17:53                       ` Ingo Molnar
2009-11-20  8:20   ` Li Zefan [this message]
2009-11-20  8:20     ` Li Zefan
2009-11-20  8:54 ` [tip:perf/core] " tip-bot for Li Zefan
2009-11-20  8:54   ` tip-bot for Li Zefan
2009-11-20  8:55 ` [RFC][PATCH 1/2] " Ingo Molnar
2009-11-20  8:55   ` Ingo Molnar
2009-11-20  9:11   ` Li Zefan
2009-11-20  9:11     ` Li Zefan

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=4B065169.7080603@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=acme@redhat.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 \
    --cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.