From: Muli Baron <muli.baron@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-rt-users@vger.kernel.org
Subject: Re: CONFIG_NO_HZ_FULL + CONFIG_PREEMPT_RT_FULL = nogo
Date: Sat, 21 Dec 2013 19:21:13 +0200 [thread overview]
Message-ID: <52B5CE09.5030908@gmail.com> (raw)
In-Reply-To: <1387617104.30230.7.camel@marge.simpson.net>
On 21/12/2013 11:11, Mike Galbraith wrote:
>
> Works, modulo noisy workqueues.
>
> rtbox:~ # sleep 35 && killall pert& cgexec -g cpuset:rtcpus taskset -c 3 pert 5
> [1] 5660
> 2400.05 MHZ CPU
> perturbation threshold 0.018 usecs.
> pert/s: 33 >15.75us: 2 min: 0.04 max: 24.14 avg: 2.51 sum/s: 84us overhead: 0.01%
> pert/s: 35 >15.54us: 3 min: 0.04 max: 24.89 avg: 2.39 sum/s: 84us overhead: 0.01%
> pert/s: 30 >15.27us: 2 min: 0.04 max: 23.03 avg: 2.64 sum/s: 80us overhead: 0.01%
> pert/s: 34 >15.12us: 3 min: 0.04 max: 25.03 avg: 2.51 sum/s: 86us overhead: 0.01%
> pert/s: 31 >14.93us: 2 min: 0.04 max: 23.86 avg: 2.60 sum/s: 83us overhead: 0.01%
> Terminated
>
I can confirm this works for me as well, but I have noticed some strange behavior under certain
conditions.
If I run a process with SCHED_OTHER priority and pin it to a specific CPU like Mike did then all is
well and everything functions as expected. If however I mask the execution of ksoftirqd by running
that process as SCHED_FIFO for too long (say a few seconds) and later I free the CPU, then what I'm
seeing is that the tick is never turned off again even though the CPU is completely idle, and
running that same SCHED_OTHER process from before now gets 1K timer interrupts/s. I suspect this has
something to do with the timer softirq never running on that CPU again as a result of this patch.
Following is trace output during this condition for two consecutive ticks, when the CPU is
completely idle (shielded by isolcpus, HZ=1000):
<idle>-0 [003] d..h3.. 355.620760: hrtimer_cancel: hrtimer=ffff88011fd8b720
<idle>-0 [003] d..h2.. 355.620760: hrtimer_expire_entry: hrtimer=ffff88011fd8b720
function=tick_sched_timer now=355487000349
<idle>-0 [003] d..h2.. 355.620761: hrtimer_expire_exit: hrtimer=ffff88011fd8b720
<idle>-0 [003] d..h3.. 355.620761: hrtimer_start: hrtimer=ffff88011fd8b720
function=tick_sched_timer expires=355488000000 softexpires=355488000000
<idle>-0 [003] ....2.. 355.620762: cpu_idle: state=4294967295 cpu_id=3
<idle>-0 [003] d...2.. 355.620762: cpu_idle: state=1 cpu_id=3
<idle>-0 [003] d..h3.. 355.621760: hrtimer_cancel: hrtimer=ffff88011fd8b720
<idle>-0 [003] d..h2.. 355.621761: hrtimer_expire_entry: hrtimer=ffff88011fd8b720
function=tick_sched_timer now=355488000330
<idle>-0 [003] d..h2.. 355.621761: hrtimer_expire_exit: hrtimer=ffff88011fd8b720
<idle>-0 [003] d..h3.. 355.621761: hrtimer_start: hrtimer=ffff88011fd8b720
function=tick_sched_timer expires=355489000000 softexpires=355489000000
<idle>-0 [003] ....2.. 355.621762: cpu_idle: state=4294967295 cpu_id=3
<idle>-0 [003] d...2.. 355.621762: cpu_idle: state=1 cpu_id=3
--Muli
next prev parent reply other threads:[~2013-12-21 17:21 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 14:07 CONFIG_NO_HZ_FULL + CONFIG_PREEMPT_RT_FULL = nogo Mike Galbraith
2013-11-06 17:49 ` Thomas Gleixner
2013-11-07 3:26 ` Mike Galbraith
2013-11-07 4:31 ` Mike Galbraith
2013-11-07 11:21 ` Thomas Gleixner
2013-11-07 12:59 ` Frederic Weisbecker
2013-11-07 13:13 ` Thomas Gleixner
2013-11-12 8:06 ` Mike Galbraith
2013-11-12 9:28 ` Thomas Gleixner
2013-11-15 16:30 ` [PATCH] rtmutex: take the waiter lock with irqs off Sebastian Andrzej Siewior
2013-11-15 20:14 ` [PATCH v2] " Sebastian Andrzej Siewior
2013-11-18 14:10 ` Peter Zijlstra
2013-11-18 17:56 ` Peter Zijlstra
2013-11-18 23:59 ` Frederic Weisbecker
2013-11-19 8:30 ` Peter Zijlstra
2013-11-22 13:59 ` Sebastian Andrzej Siewior
2013-11-22 16:08 ` Peter Zijlstra
2013-11-22 16:21 ` Sebastian Andrzej Siewior
2013-11-22 17:44 ` Sebastian Andrzej Siewior
2013-11-25 18:33 ` Paul Gortmaker
2013-11-07 13:07 ` CONFIG_NO_HZ_FULL + CONFIG_PREEMPT_RT_FULL = nogo Mike Galbraith
2013-12-20 15:41 ` Sebastian Andrzej Siewior
2013-12-21 9:11 ` Mike Galbraith
2013-12-21 17:21 ` Muli Baron [this message]
2013-12-22 4:17 ` Mike Galbraith
2013-12-22 5:10 ` Mike Galbraith
2013-12-22 5:37 ` Mike Galbraith
2013-12-22 5:16 ` Mike Galbraith
2013-11-08 3:23 ` Paul E. McKenney
2013-11-08 7:31 ` Mike Galbraith
2013-11-08 12:37 ` Paul E. McKenney
2013-11-08 13:26 ` Mike Galbraith
2013-11-08 14:03 ` Paul E. McKenney
2013-11-08 14:21 ` Mike Galbraith
2013-11-08 14:29 ` Frederic Weisbecker
2013-11-08 14:45 ` Paul E. McKenney
2013-11-08 16:03 ` Frederic Weisbecker
2013-11-08 14:53 ` Mike Galbraith
2013-11-08 16:04 ` Frederic Weisbecker
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=52B5CE09.5030908@gmail.com \
--to=muli.baron@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
/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).