From: Rik van Riel <riel@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Clark Williams <clark.williams@gmail.com>,
Luiz Capitulino <lcapitulino@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -rt] timer: upper bound on loops of __run_timers processing
Date: Tue, 30 Dec 2014 16:05:36 -0500 [thread overview]
Message-ID: <54A313A0.7050807@redhat.com> (raw)
In-Reply-To: <20141230195228.GA3057@amt.cnet>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/30/2014 02:52 PM, Marcelo Tosatti wrote:
>
> Commit "timers: do not raise softirq unconditionally", allows for
> timer wheel processing (__run_timers) to be delayed for long
> periods of time.
>
> The effect is that
>
> loops = jiffies - base->timer_jiffies
>
> Can grow to very large values resulting in __run_timers taking
> hundreds of milliseconds to execute.
>
> Fix by creating an upper bound on the number of loops to be
> processed. This allows a nohz=off kernel to achieve desired
> latencies.
>
> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
>
> diff --git a/kernel/timer.c b/kernel/timer.c index f59e18c..c128416
> 100644 --- a/kernel/timer.c +++ b/kernel/timer.c @@ -1488,6
> +1488,12 @@ void run_local_timers(void) } #endif
>
> + if (time_after_eq(jiffies, base->timer_jiffies)) { + unsigned
> long jiffies_delta = jiffies - base->timer_jiffies; + if
> (jiffies_delta > TVR_SIZE) + raise_softirq(TIMER_SOFTIRQ); + }
It certainly looks like cascading the timers over and over and
over again could be a lot of work.
Acked-by: Rik van Riel <riel@redhat.com>
- --
All rights reversed
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJUoxOfAAoJEM553pKExN6DO+0H/i2TXS2DJ6cObGZytYhsRz/U
4oqH4eCjwK5JczFMsyoUh/kXIkEQukMudj74katoP0TARlcnZF2G+R/Hj4XccCpz
X84DI7SCFZIwl3gpiuOoR81mosd1VkLBouwYj1Aglt+5Sh63yq91lreX20Tw/swF
jlorAWAAblQdt2zC5smjtbbhfKMuPC8qJFGoiGmLLPC/1l9XmGmfymB2WfN8IZm4
DrqAlCSm8+xxGdwUwAZTuHuHX15VOpGuUuEV2E8BM+6G93HI8iJe5E7g5hRymcNp
NPCe+BFgZ9AxHqNokC1cSWrqaS3koBbTJRDKAqxSEptmYQMZ/a61ydYJQmBtImw=
=uqAv
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-12-30 21:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 19:52 [PATCH -rt] timer: upper bound on loops of __run_timers processing Marcelo Tosatti
2014-12-30 21:05 ` Rik van Riel [this message]
2015-01-14 17:21 ` Marcelo Tosatti
2015-01-14 17:41 ` Steven Rostedt
2015-01-26 21:12 ` Marcelo Tosatti
2015-02-17 17:24 ` Sebastian Andrzej Siewior
2015-02-17 23:08 ` Rik van Riel
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=54A313A0.7050807@redhat.com \
--to=riel@redhat.com \
--cc=clark.williams@gmail.com \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.