From: Carsten Emde <C.Emde@osadl.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
RT-users <linux-rt-users@vger.kernel.org>,
Carsten Emde <C.Emde@osadl.org>
Subject: [PATCH 1/2] add-tracing_max_latency-may-not-be-worst-case-system-latency-to-ftrace-docs.patch
Date: Sat, 26 Dec 2009 22:41:15 +0100 [thread overview]
Message-ID: <20091226214229.238699028@osadl.org> (raw)
In-Reply-To: <20091226214114.843059850@osadl.org>
[-- Attachment #1: add-tracing_max_latency-may-not-be-worst-case-system-latency-to-ftrace-docs.patch --]
[-- Type: text/plain, Size: 1740 bytes --]
Explain the background of the trace variable
tracing_max_latency in the context of the
wakeup and the wakeup_rt tracer and why it
does not necessarily measure the worst-case
latency of the system.
Signed-off-by: Carsten Emde <C.Emde@osadl.org>
Index: linux-2.6.33-rc2/Documentation/trace/ftrace.txt
===================================================================
--- linux-2.6.33-rc2.orig/Documentation/trace/ftrace.txt
+++ linux-2.6.33-rc2/Documentation/trace/ftrace.txt
@@ -117,9 +117,25 @@ of ftrace. Here is a list of some of the
For example, the time interrupts are disabled.
This time is saved in this file. The max trace
will also be stored, and displayed by "trace".
- A new max trace will only be recorded if the
+ A new max trace will only be recorded, if the
latency is greater than the value in this
- file. (in microseconds)
+ file (in microseconds). NOTE: The max latency
+ recorded by the wakeup and the wakeup_rt tracer
+ do not necessarily reflect the worst-case latency
+ of the system. If two or more processes share the
+ highest priority of the system and may be woken
+ up shortly after each other, the max latency
+ recorded by the wakeup and the wakeup_rt tracers
+ equal the worst-case latency of the system *plus*
+ the longest possible runtime duration of all tasks
+ that share the same priority. An exact measurement
+ of the worst-case wakeup latency of the system can
+ be achieved using the wakekup latency histograms
+ that are part of the PREEMPT_RT patches. These
+ histograms separately determine the wakeup latency
+ of a task that exclusively uses the highest
+ priority of the system and of tasks that share the
+ highest priority of the system with other tasks.
buffer_size_kb:
next prev parent reply other threads:[~2009-12-26 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-26 21:41 [PATCH 0/2] tracing: Expand ftrace documentation Carsten Emde
2009-12-26 21:41 ` Carsten Emde [this message]
2009-12-26 21:41 ` [PATCH 2/2] add-trace_clock-to-ftrace-docs.patch Carsten Emde
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=20091226214229.238699028@osadl.org \
--to=c.emde@osadl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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®