From: Gratian Crisan <gratian.crisan@ni.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Gratian Crisan <gratian.crisan@ni.com>,
Piotr Gregor <piotrgregor@rsyncme.org>,
tglx@linutronix.de, Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH RT] time/hrtimer: Use softirq based wakeups for non-RT threads
Date: Thu, 05 Oct 2017 16:14:49 -0500 [thread overview]
Message-ID: <87d161pa9i.fsf@kerf.amer.corp.natinst.com> (raw)
In-Reply-To: <20171004160820.27754-1-bigeasy@linutronix.de>
Sebastian Andrzej Siewior writes:
> Normal wake ups (like clock_nanosleep()) which are performed by normal
> users can easily lead to 2ms latency spikes if (enough) hrtimer wakeups
> are synchronized.
> This patch moves all hrtimers wakeups to the softirq queue unless the
> caller has a RT priority.
>
> Reported-by: Gratian Crisan <gratian.crisan@ni.com>
I can confirm this patch fixes the original problem reported.
I ran an overnight test (about 30 hours total) on two platforms using
cyclictest + hrtimer stress load: configurable number of SCHED_OTHER
threads doing random clock_nanosleep() in up to 1 mS intervals.
Without this patch the max latency recorded was:
* on dual core, Intel Atom E3825 @ 1.33GHz: 107 uS
* on dual core, Zynq 7020 @ 667MHz: 261 uS
With this patch the max numbers drop to:
* on dual core, Intel Atom E3825 @ 1.33GHz: 66 uS
* on dual core, Zynq 7020 @ 667MHz: 90 uS
The max latency numbers with this patch are in-line with expectations
for these platforms.
Thank you so much,
-Gratian
prev parent reply other threads:[~2017-10-05 21:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 16:08 Sebastian Andrzej Siewior
2017-10-05 21:14 ` Gratian Crisan [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=87d161pa9i.fsf@kerf.amer.corp.natinst.com \
--to=gratian.crisan@ni.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=piotrgregor@rsyncme.org \
--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®