From: Marcelo Tosatti <mtosatti@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Clark Williams <clark.williams@gmail.com>,
Luiz Capitulino <lcapitulino@redhat.com>,
Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: [PATCH -rt] timer: upper bound on loops of __run_timers processing
Date: Wed, 14 Jan 2015 15:21:47 -0200 [thread overview]
Message-ID: <20150114172147.GA16570@amt.cnet> (raw)
In-Reply-To: <20141230195228.GA3057@amt.cnet>
Ping?
On Tue, Dec 30, 2014 at 05:52:28PM -0200, 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);
> + }
> +
> if (!base->active_timers)
> goto out;
>
next parent reply other threads:[~2015-01-14 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20141230195228.GA3057@amt.cnet>
2015-01-14 17:21 ` Marcelo Tosatti [this message]
2015-01-14 17:41 ` [PATCH -rt] timer: upper bound on loops of __run_timers processing Steven Rostedt
2015-01-26 21:12 ` Marcelo Tosatti
2015-02-17 17:24 ` Sebastian Andrzej Siewior
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=20150114172147.GA16570@amt.cnet \
--to=mtosatti@redhat.com \
--cc=clark.williams@gmail.com \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=riel@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;
as well as URLs for NNTP newsgroup(s).