From: Carsten Emde <C.Emde@osadl.org>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Binoy Jayan <binoy.jayan@linaro.org>,
"Steven Rostedt (Red Hat)" <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Daniel Wagner <daniel.wagner@bmw-carit.de>,
Arnd Bergmann <arnd@arndb.de>,
Masami <masami.hiramatsu@linaro.org>
Subject: Re: [PATCH v6 4/4] tracing: Histogram for delayed hrtimer offsets
Date: Fri, 23 Sep 2016 16:20:44 +0200 [thread overview]
Message-ID: <4877f67c-bd18-1811-2932-1c2fda47c0e4@osadl.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1609091521390.5679@nanos>
On 09/09/2016 03:30 PM, Thomas Gleixner wrote:
> On Thu, 8 Sep 2016, Binoy Jayan wrote:
>> On 8 September 2016 at 12:40, Thomas Gleixner <tglx@linutronix.de> wrote:
> [..]
>>>> + latency = ktime_to_ns(ktime_sub(basenow,
>>>> + ktime_to_ns(timer->praecox) ?
>>>> + timer->praecox : hrtimer_get_expires(timer)));
>>>> + task = timer->function == hrtimer_wakeup ?
>>>> + container_of(timer, struct hrtimer_sleeper,
>>>> + timer)->task : NULL;
>>>
>>> This is a complete horrible hack. You're tying the task evaluation into a
>>> single instance of hrtimer users. What's the justification for this and why
>>> do you need task at all?
Makes only sense, if any, if wakeup latency histograms that store the task with
the highest latency so far are available. Initially, I wanted to give a short
explanation here why such internal histograms may be useful, but I found it
easier in a format where pictures of example latency plots and recordings can
be shown. So I wrote a short article on "Preemption latency of real-time Linux
systems" -> https://www.osadl.org/Single-View.111+M5246ebc55e3.0.html.
Hope this helps,
-Carsten.
next prev parent reply other threads:[~2016-09-23 15:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 11:13 [PATCH v6 0/4] *** Latency histograms - IRQSOFF,PREEMPTOFF, Delayed HRTIMERS *** Binoy Jayan
2016-09-07 11:13 ` [PATCH v6 1/4] tracing: Deference pointers without RCU checks Binoy Jayan
2016-09-08 6:46 ` Masami Hiramatsu
2016-09-07 11:13 ` [PATCH v6 2/4] tracing: Add hist trigger support for generic fields Binoy Jayan
2016-09-07 13:39 ` kbuild test robot
2016-09-07 11:13 ` [PATCH v6 3/4] tracing: Add trace_irqsoff tracepoints Binoy Jayan
2016-09-07 16:42 ` Thomas Gleixner
2016-09-08 5:20 ` Daniel Wagner
2016-09-08 6:31 ` Thomas Gleixner
2016-09-08 8:06 ` Thomas Gleixner
2016-09-12 13:50 ` Steven Rostedt
2016-09-14 6:52 ` Binoy Jayan
2016-09-14 9:42 ` Thomas Gleixner
2016-09-07 11:13 ` [PATCH v6 4/4] tracing: Histogram for delayed hrtimer offsets Binoy Jayan
2016-09-08 6:56 ` Masami Hiramatsu
2016-09-08 7:10 ` Thomas Gleixner
2016-09-08 9:39 ` Binoy Jayan
2016-09-09 13:30 ` Thomas Gleixner
2016-09-23 14:20 ` Carsten Emde [this message]
2016-09-09 17:10 ` Mark Brown
2016-09-10 6:10 ` Thomas Gleixner
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=4877f67c-bd18-1811-2932-1c2fda47c0e4@osadl.org \
--to=c.emde@osadl.org \
--cc=arnd@arndb.de \
--cc=binoy.jayan@linaro.org \
--cc=daniel.wagner@bmw-carit.de \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu@linaro.org \
--cc=mingo@redhat.com \
--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®