All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: mingo@kernel.org
Cc: josh@joshtriplett.org, peterz@infradead.org, oleg@redhat.com,
	rostedt@goodmis.org, bitbucket@online.de, tglx@linutronix.de,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL timers] Timer-wheel bandaids^Wcommits
Date: Wed, 29 Jan 2014 15:39:36 -0800	[thread overview]
Message-ID: <20140129233936.GA11150@linux.vnet.ibm.com> (raw)

Hello, 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.

Each of these commits has at least two Reviewed-by, one Acked-by, and
one Tested-by tag, so they are ready for more extensive testing in -tip.

							Thanx, Paul

The following changes since commit 00e2bcd6d35f59fce7fa0e76e24d08f74c6a8506:

  clocksource: Timer-sun5i: Switch to sched_clock_register() (2014-01-19 13:23:23 +0100)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/timers

for you to fetch changes up to 6f089d0be7fef9705b3a7755b05d1092e772b910:

  timers: Make internal_add_timer() update ->next_timer if ->active_timers == 0 (2014-01-29 15:25:16 -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(-)


             reply	other threads:[~2014-01-29 23:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-29 23:39 Paul E. McKenney [this message]
2014-01-30  5:44 ` [GIT PULL timers] Timer-wheel bandaids^Wcommits Preeti Murthy
2014-01-30  8:48   ` 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=20140129233936.GA11150@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 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.