From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: tglx@linutronix.de, mingo@kernel.org
Cc: linux-kernel@vger.kernel.org, josh@joshtriplett.org,
peterz@infradead.org, oleg@redhat.com, rostedt@goodmis.org,
bitbucket@online.de
Subject: [GIT PULL timers] Timer-wheel bandaids^Wcommits for 3.15
Date: Thu, 27 Feb 2014 17:27:04 -0800 [thread overview]
Message-ID: <20140228012704.GA20805@linux.vnet.ibm.com> (raw)
Hello, Thomas and Ingo,
This pull request contains latency bandaids^Woptimizations to the
timer-wheel code that are useful in conjunction with NO_HZ_FULL Kconfig
option. These optimizations reduce the jiffy-by-jiffy looping in cases
where there is either zero or one timers in the timer wheel, which is
a common case for NO_HZ_FULL "worker" CPUs that run almost entirely
in usermode for a single task.
This is of course no substitute for a more extensive reworking of the
timer-wheel code, but it does provide some simple patches that can
provide significant latency improvements for NO_HZ_FULL systems that
have CPUs that very rarely enter the kernel.
Thanx, Paul
These changes since commit 849401b66d305f3feb75b6db7459b95ad190552a:
tick: Fixup more fallout from hrtimer broadcast mode (2014-02-09 15:11:47 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git timers.2014.02.25a
for you to fetch changes up to aea369b959bef10d235cd0714789cd8b0fe170b8:
timers: Make internal_add_timer() update ->next_timer if ->active_timers == 0 (2014-02-25 12:39:01 -0800)
----------------------------------------------------------------
Oleg Nesterov (1):
timers: Make internal_add_timer() update ->next_timer if ->active_timers == 0
Paul E. McKenney (4):
timers: Track total number of timers in list
timers: Reduce __run_timers() latency for empty list
timers: Reduce future __run_timers() latency for newly emptied list
timers: Reduce future __run_timers() latency for first add to empty list
kernel/timer.c | 30 ++++++++++++++++++++++++++++--
1 file changed, 28 insertions(+), 2 deletions(-)
next reply other threads:[~2014-02-28 1:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 1:27 Paul E. McKenney [this message]
2014-02-28 5:06 ` [GIT PULL timers] Timer-wheel bandaids^Wcommits for 3.15 Mike Galbraith
2014-02-28 16:10 ` Paul E. McKenney
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=20140228012704.GA20805@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=bitbucket@online.de \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.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