public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@fifo99.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Theodore Tso <tytso@mit.edu>,
	Arjan van de Ven <arjan@infradead.org>,
	Hua Zhong <hzhong@gmail.com>
Subject: Re: [PATCH 0/4] trace: profiling branches
Date: Sun, 30 Nov 2008 02:58:56 -0800	[thread overview]
Message-ID: <1228042736.6868.19.camel@desktop> (raw)
In-Reply-To: <20081121071213.365288293@goodmis.org>

On Fri, 2008-11-21 at 02:12 -0500, Steven Rostedt wrote:
> Ingo,
> 
> The following patches clean up the unlikely/likely tracer. Namely
> it consolidates it into a single file called "profile_annotated_branch".
> 
> It also adds a new profiler. A true branch profiler that profiles all
> if() statements where the conditional is not a constant. It puts 
> a bit of overhead on the system, but the results seem pretty interesting.
> The results are placed in "profile_branch".
> 

I looked at the full version of this, and it looks really slow.. As I
recall the biggest problem with the -mm version was it's cacheline
bouncing (pointed out by Ingo), and yours doesn't _seem_ to fix that. In
fact your version looks a lot worse..

So really between the two if we want mainline likely profiling the -mm
version is a better choice.. The reason that version never went into
mainline is cause neither me or Andrew felt strongly that this was
useful in more than just -mm ..

If you look at the output from the profiling long enough it becomes
clear that it's frequently misleading .. In the short term a certain
branch might be likely, and in the long term it isn't.. So you can't
really blindly start converting the annotation..

I should also mention that I didn't write the -mm version alone, it was
an effort between three people me, Andrew, and Hua Zhong (CC added)..

Daniel


  parent reply	other threads:[~2008-11-30 11:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-21  7:12 [PATCH 0/4] trace: profiling branches Steven Rostedt
2008-11-21  7:12 ` [PATCH 1/4] trace: remove extra assign in branch check Steven Rostedt
2008-11-21  7:12 ` [PATCH 2/4] trace: consolidate unlikely and likely profiler Steven Rostedt
2008-11-21  7:12 ` [PATCH 3/4] trace: branch profiling should not print percent without data Steven Rostedt
2008-11-21  7:12 ` [PATCH 4/4] trace: profile all if conditionals Steven Rostedt
2008-11-21 23:20   ` Andrew Morton
2008-11-21 23:33     ` Steven Rostedt
2008-11-23 12:37       ` Ingo Molnar
2008-11-23 15:48   ` Ingo Molnar
2008-11-23 16:07     ` [PATCH] net/wireless/reg.c: fix Ingo Molnar
2008-11-23 19:43   ` [PATCH 4/4] trace: profile all if conditionals Andi Kleen
2008-11-23 19:56     ` Steven Rostedt
2008-11-23 20:24       ` Andi Kleen
2008-11-23 20:32         ` Steven Rostedt
2008-11-23 20:51           ` Andi Kleen
2008-11-23 21:38       ` Ingo Molnar
2008-11-30 10:58 ` Daniel Walker [this message]
2008-11-30 15:19   ` [PATCH 0/4] trace: profiling branches Steven Rostedt

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=1228042736.6868.19.camel@desktop \
    --to=dwalker@fifo99.com \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=hzhong@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=tytso@mit.edu \
    /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