From: Frederic Weisbecker <fweisbec@gmail.com>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Paul Mackerras <paulus@samba.org>,
Tom Zanussi <tzanussi@gmail.com>,
Masami Hiramatsu <mhiramat@redhat.com>
Subject: [PATCH 0/2] perf: Redesign trace events reordering
Date: Wed, 5 May 2010 02:03:29 +0200 [thread overview]
Message-ID: <1273017811-16880-1-git-send-regression-fweisbec@gmail.com> (raw)
I recently noticed that the new reordering design is broken
when it deals with tons of events.
This patchset provides another algorithm to deal with that,
tested without any problem.
And since it involves more frequent flushes, I guess it could
plug nicely with the live mode.
Frederic Weisbecker (2):
perf: Introduce a new "round of buffers read" pseudo event
perf: Provide a new deterministic events reordering algorithm
tools/perf/builtin-record.c | 34 ++++++++++----
tools/perf/util/event.h | 3 +-
tools/perf/util/session.c | 106 +++++++++++++++++++++++++++++++------------
tools/perf/util/session.h | 36 +++++++++------
4 files changed, 123 insertions(+), 56 deletions(-)
next reply other threads:[~2010-05-05 0:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 0:03 Frederic Weisbecker [this message]
2010-05-05 0:03 ` [PATCH 1/2] perf: Introduce a new "round of buffers read" pseudo event Frederic Weisbecker
2010-05-05 0:03 ` [PATCH 2/2] perf: Provide a new deterministic events reordering algorithm Frederic Weisbecker
2010-05-05 5:48 ` [PATCH 0/2] perf: Redesign trace events reordering Tom Zanussi
2010-05-08 15:54 ` Frederic Weisbecker
2010-05-10 7:21 ` [tip:perf/core] perf/live-mode: Handle payload-less events tip-bot for Tom Zanussi
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=1273017811-16880-1-git-send-regression-fweisbec@gmail.com \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=tzanussi@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®