linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "T. Smith" <tlsmith3777@gmail.com>
To: Daniel Bristot de Oliveira <bristot@redhat.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Jon Masters <jcm@redhat.com>, Carsten Emde <C.Emde@osadl.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>,
	Clark Williams <williams@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Daniel Wagner <wagi@monom.org>
Cc: linux-kernel@vger.kernel.org
Subject: runaway latency detection
Date: Sat, 20 Aug 2016 12:03:37 -0500	[thread overview]
Message-ID: <94710CE6-857F-424A-9D50-8569D6282367@gmail.com> (raw)

Trying to isolate PREEMPT_RT (full preemption) runaway latency conditions seen when using the cyclictest on the 4.1.8 SMP PREEMPT_RT kernel.  Seen average latency of 3uS, but runaway or outlier max latency seems indeterminate.  Noted 72uS with one run of the cyclictest for example. Is this a known issue, the cause understood, and is there a patch for this?  

The goal is to isolate causes of indeterminism when using the PREEMPT_RT kernel configuration with full preemption and to characterize latency and jitter using ftrace, any recommendations?

             reply	other threads:[~2016-08-20 17:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-20 17:03 T. Smith [this message]
2016-08-20 17:54 ` runaway latency detection Nikolay Borisov
     [not found]   ` <CAChUvXP8Zy4uz95NWFEtF9oU6rHjPZ0Uz5qPMqY1n3i2eBeaSw@mail.gmail.com>
2016-08-21  3:45     ` Steven Rostedt
2016-08-22  2:22 T. Smith

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=94710CE6-857F-424A-9D50-8569D6282367@gmail.com \
    --to=tlsmith3777@gmail.com \
    --cc=C.Emde@osadl.org \
    --cc=akpm@linux-foundation.org \
    --cc=bigeasy@linutronix.de \
    --cc=bristot@redhat.com \
    --cc=jcm@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=wagi@monom.org \
    --cc=williams@redhat.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;
as well as URLs for NNTP newsgroup(s).