From: fche@redhat.com (Frank Ch. Eigler)
To: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Tim Bird <tim.bird@am.sony.com>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Li Zefan <lizf@cn.fujitsu.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/4] ftrace - add function_duration tracer
Date: Thu, 10 Dec 2009 12:28:46 -0500 [thread overview]
Message-ID: <y0md42magc1.fsf@fche.csb> (raw)
In-Reply-To: <20091210153845.GA28230@elte.hu> (Ingo Molnar's message of "Thu, 10 Dec 2009 16:38:45 +0100")
Ingo Molnar <mingo@elte.hu> writes:
> [...]
> Just off the top of my head we want to be able to trace:
>
> - max irq service latencies for a given IRQ
> - max block IO completion latencies for a app
> - max TLB flush latencies in the system
> - max sys_open() latencies in a task
> - max fork()/exit() latencies in a workload
> - max scheduling latencies on a given CPU
> - max page fault latencies
> - max wakeup latencies for a given task
> - max memory allocation latencies
>
> - ... and dozens and dozens of other things where there's a "start"
> and a "stop" event and where we want to measure the time between
> them.
> [...]
FWIW, those who want to collect such measurements today can do so with
a few lines of systemtap script for each of the above.
- FChE
next prev parent reply other threads:[~2009-12-10 17:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 22:40 [PATCH 2/4] ftrace - add function_duration tracer Tim Bird
2009-12-10 7:08 ` Ingo Molnar
2009-12-10 12:03 ` Frederic Weisbecker
2009-12-10 14:11 ` Ingo Molnar
2009-12-10 14:53 ` Steven Rostedt
2009-12-10 15:38 ` Ingo Molnar
2009-12-10 16:22 ` Steven Rostedt
2009-12-10 16:52 ` Ingo Molnar
2009-12-10 17:16 ` Steven Rostedt
2009-12-10 17:28 ` Frank Ch. Eigler [this message]
2009-12-10 17:57 ` Ingo Molnar
2009-12-10 18:04 ` Frank Ch. Eigler
2009-12-10 18:35 ` Ingo Molnar
2009-12-10 18:50 ` Frank Ch. Eigler
2009-12-10 20:14 ` Ingo Molnar
2009-12-10 21:30 ` Frank Ch. Eigler
2009-12-10 14:29 ` Steven Rostedt
2009-12-10 16:16 ` Ingo Molnar
2009-12-10 20:23 ` Frederic Weisbecker
2009-12-10 21:55 ` Steven Rostedt
2009-12-10 22:40 ` Frederic Weisbecker
2009-12-10 21:13 ` Tim Bird
2009-12-10 22:04 ` Steven Rostedt
2009-12-10 22:26 ` Tim Bird
2009-12-10 22:36 ` Tim Bird
2009-12-10 23:47 ` 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=y0md42magc1.fsf@fche.csb \
--to=fche@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tim.bird@am.sony.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