From: David Ahern <dsahern@gmail.com>
To: Don Zickus <dzickus@redhat.com>
Cc: acme@kernel.org, linux-kernel@vger.kernel.org,
Jiri Olsa <jolsa@redhat.com>,
jmario@redhat.com
Subject: Re: [PATCH] perf tool: Fix ppid for synthesized fork events
Date: Tue, 24 Mar 2015 15:12:41 -0600 [thread overview]
Message-ID: <5511D349.7070508@gmail.com> (raw)
In-Reply-To: <20150324201020.GH199787@redhat.com>
On 3/24/15 2:10 PM, Don Zickus wrote:
> He does this with and without the patch. The difference is usually over 50%
> extra time with the patch for both the record timings and report timings.:-(
I find that shocking. The patch only populates ppid and ptid with a
value read from the file that is already opened and processed. Most of
the patch is just plumbing the value from the low level function that
processes the status file back to synthesize_fork.
What benchmark is this? Is it something I can download and run? if so,
details? site, command, args?
Thanks,
David
next prev parent reply other threads:[~2015-03-24 21:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 17:41 [PATCH] perf tool: Fix ppid for synthesized fork events David Ahern
2015-03-19 20:56 ` Don Zickus
2015-03-19 21:06 ` David Ahern
2015-03-20 14:01 ` Arnaldo Carvalho de Melo
2015-03-24 20:10 ` Don Zickus
2015-03-24 21:12 ` David Ahern [this message]
2015-03-25 12:22 ` Joe Mario
2015-03-25 13:24 ` Arnaldo Carvalho de Melo
2015-03-25 15:03 ` David Ahern
2015-03-25 19:20 ` Don Zickus
2015-03-25 16:57 ` David Ahern
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=5511D349.7070508@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@kernel.org \
--cc=dzickus@redhat.com \
--cc=jmario@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).