public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Bird <tim.bird@am.sony.com>
To: "rostedt@goodmis.org" <rostedt@goodmis.org>
Cc: "Bird, Tim" <Timothy.Bird@am.sony.com>,
	linux kernel <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 4/4] ftrace - function_duration Documentation
Date: Thu, 10 Dec 2009 13:21:52 -0800	[thread overview]
Message-ID: <4B216670.60807@am.sony.com> (raw)
In-Reply-To: <1260416840.2146.134.camel@gandalf.stny.rr.com>

Steven Rostedt wrote:
> On Wed, 2009-12-09 at 14:42 -0800, Tim Bird wrote:
>> Documentation for function_duration tracer.
> 
>> +The purpose of the function duration tracer is to help find the
>> +longest-running, most time-consuming functions in the Linux kernel.
>> +This is especially important for early initialization, to reduce
>> +kernel boot time.
>> +
>> +Function duration tracing uses the ftrace ability to hook both the
>> +entry and exit of a function, to record duration information for
>> +kernel functions.  This is similar to the function_graph tracer, but
>> +the function_duration tracer is specially written to support filtering
>> +by duration and decreased tracer overhead while filtering.
>> +
>> +This extends the amount of time that a trace can cover, and reduces
>> +interference with the timing of the traced activity.
> 
> BTW, have you taken a look at the function profiler? It also keeps track
> of all durations without using the ring buffer. It just adds them up and
> gives an average time.

I haven't, but I should.  However, my tool has some other options
(like subtracting time spent in interrupts) that I don't
think the profile approach currently supports.
 -- Tim

=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Corporation of America
=============================


      reply	other threads:[~2009-12-10 21:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09 22:42 [PATCH 4/4] ftrace - function_duration Documentation Tim Bird
2009-12-10  3:47 ` Steven Rostedt
2009-12-10 21:21   ` Tim Bird [this message]

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=4B216670.60807@am.sony.com \
    --to=tim.bird@am.sony.com \
    --cc=Timothy.Bird@am.sony.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.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