From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Lin Ming <ming.m.lin@intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 -tip] perf probe: Add fastpath to do lookup by function name
Date: Thu, 24 Mar 2011 23:57:52 -0300 [thread overview]
Message-ID: <20110325025752.GB11195@ghostprotocols.net> (raw)
In-Reply-To: <4D8BEC71.1040404@hitachi.com>
Em Fri, Mar 25, 2011 at 10:14:25AM +0900, Masami Hiramatsu escreveu:
> (2011/03/24 23:09), Lin Ming wrote:
> > v2 -> v1:
> > - Don't compare file names with cu_find_realpath(...), instead, compare them
> > with the name returned by dwarf_decl_file(sp_die)
> >
> > The vmlinux file may have thousands of CUs.
> > We can lookup function name from .debug_pubnames section
> > to avoid the slow loop on CUs.
> >
> > ./perf stat -r 10 -- ./perf probe -k /home/mlin/vmlinux \
> > -s /home/mlin/linux-2.6 \
> > --line csum_partial_copy_to_user > tmp.log
> >
> > before patch applied
> > =====================
> > 364.535892 task-clock-msecs # 0.997 CPUs
> > 0 context-switches # 0.000 M/sec
> > 0 CPU-migrations # 0.000 M/sec
> > 29,993 page-faults # 0.082 M/sec
> > 865,862,109 cycles # 2375.245 M/sec
> > 1,255,259,630 instructions # 1.450 IPC
> > 252,400,884 branches # 692.390 M/sec
> > 3,429,376 branch-misses # 1.359 %
> > 1,386,990 cache-references # 3.805 M/sec
> > 687,188 cache-misses # 1.885 M/sec
> >
> > 0.365792170 seconds time elapsed
> >
> > after patch applied
> > =====================
> > 89.896405 task-clock-msecs # 0.991 CPUs
> > 1 context-switches # 0.000 M/sec
> > 0 CPU-migrations # 0.000 M/sec
> > 10,145 page-faults # 0.113 M/sec
> > 214,553,875 cycles # 2386.679 M/sec
> > 226,915,559 instructions # 1.058 IPC
> > 44,536,614 branches # 495.422 M/sec
> > 613,074 branch-misses # 1.377 %
> > 860,787 cache-references # 9.575 M/sec
> > 442,380 cache-misses # 4.921 M/sec
> >
> > 0.090716032 seconds time elapsed
>
> Thanks! Looks very good :)
>
> Acked-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Indeed, I'll try and process this one tomorrow,
Thanks a lot!
- Arnaldo
next prev parent reply other threads:[~2011-03-25 2:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 15:38 [PATCH] perf probe: Add fastpath to do lookup by function name Lin Ming
2011-03-24 7:58 ` Ingo Molnar
2011-03-24 8:38 ` Lin Ming
2011-03-24 8:47 ` Ingo Molnar
2011-03-24 9:08 ` Masami Hiramatsu
2011-03-24 13:47 ` Lin Ming
2011-03-24 14:09 ` [PATCH v2 -tip] " Lin Ming
2011-03-25 1:14 ` Masami Hiramatsu
2011-03-25 2:57 ` Arnaldo Carvalho de Melo [this message]
2011-03-25 6:33 ` Lin Ming
2011-03-25 8:30 ` Lin Ming
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=20110325025752.GB11195@ghostprotocols.net \
--to=acme@infradead.org \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
/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