All of lore.kernel.org
 help / color / mirror / Atom feed
From: Waiman Long <Waiman.Long@hp.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	Jiri Olsa <jolsa@redhat.com>,
	Stephane Eranian <eranian@google.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org, "Chandramouleeswaran,
	Aswin" <aswin@hp.com>, "Norton, Scott J" <scott.norton@hp.com>,
	Fr??d??ric Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH] perf: fix symbol processing bug and greatly improve performance
Date: Tue, 07 May 2013 10:52:28 -0400	[thread overview]
Message-ID: <5189152C.4010703@hp.com> (raw)
In-Reply-To: <51890D71.9080600@hp.com>

On 05/07/2013 10:19 AM, Waiman Long wrote:
> The slowdown that I was trying to fix was in the "perf record" part of 
> the profiling process, not the "perf report" part. I didn't try 
> perf-record on perf-record as the performance counters are limited 
> resources and I don't want resource conflicts to affect the results. 
> As the slow-down was entirely in the user space, I decided to use 
> gprof to do the profiling.

Just to clarify that the post-processing time that I referred to in the 
patch is the time spent after the workload finishes in the perf-record 
session and the perf command itself quits. I could take a really long 
time for perf to quit without the patch.

Regards,
Longman


  reply	other threads:[~2013-05-07 14:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-06 13:43 [PATCH] perf: fix symbol processing bug and greatly improve performance Waiman Long
2013-05-07  7:01 ` Ingo Molnar
2013-05-07 14:19   ` Waiman Long
2013-05-07 14:52     ` Waiman Long [this message]
2013-05-07 17:15     ` Ingo Molnar
2013-05-07  9:30 ` Jiri Olsa
2013-05-07 14:40   ` Waiman Long
2013-05-08 15:44   ` Waiman Long
2013-05-09 10:19     ` Jiri Olsa
2013-05-09 12:52       ` Ingo Molnar
2013-05-09 14:46       ` Waiman Long
2013-05-09 15:05         ` David Ahern
2013-05-09 15:31           ` Waiman Long

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=5189152C.4010703@hp.com \
    --to=waiman.long@hp.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=aswin@hp.com \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=paulus@samba.org \
    --cc=scott.norton@hp.com \
    /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.