All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: [GIT PULL] timers update for 3.15
Date: Thu, 27 Feb 2014 13:53:09 +0100	[thread overview]
Message-ID: <20140227125306.GA17608@localhost.localdomain> (raw)
In-Reply-To: <20140227121707.GE9712@gmail.com>

On Thu, Feb 27, 2014 at 01:17:07PM +0100, Ingo Molnar wrote:
> 
> * Frederic Weisbecker <fweisbec@gmail.com> wrote:
> 
> > Ingo,
> > 
> > Please pull the timers/core branch that can be found at:
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> > 	timers/core
> > ---
> > 
> > * The patch from Viresh removes some unecessary scheduler IPIs that wake
> >   up the CPUs when deferrable timers are enqueued on remote targets.
> > 
> >   In practice I have seen on boot some of these IPIs from various
> >   sources:  MCE, vmstat/SLAB, cpufreq. They happen either on initcall
> >   or cpu hotplug. Since these timers are enqueued on all CPUs, there
> >   are some potential big rounds of IPIs that are spared with this patch.
> >   
> >   But it's just what I've seen on my own machine on boot. I expect some
> >   more scenarios where a few IPIs will be avoided depending on configs
> >   and usecases because we have some more users of deferrable timers.
> > 
> > * Kconfig text made clearer for full dynticks by Paul Gortmaker.
> > 
> > Thanks,
> > 	Frederic
> > ---
> > 
> > Paul Gortmaker (1):
> >       nohz: ensure users are aware boot CPU is not NO_HZ_FULL
> > 
> > Viresh Kumar (1):
> >       timer: Spare IPI when deferrable timer is queued on idle remote targets
> > 
> > 
> >  kernel/time/Kconfig | 2 +-
> >  kernel/timer.c      | 9 ++++++++-
> >  2 files changed, 9 insertions(+), 2 deletions(-)
> 
> So I wanted to pull this fine set of commits, just to discover that 
> Thomas already pulled it into timers/core :-)

Ah! Now I understand why it was pulled silently in the evening ;)

      reply	other threads:[~2014-02-27 12:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 16:52 [GIT PULL] timers update for 3.15 Frederic Weisbecker
2014-02-26 16:52 ` [PATCH 1/2] timer: Spare IPI when deferrable timer is queued on idle remote targets Frederic Weisbecker
2014-02-26 16:52 ` [PATCH 2/2] nohz: ensure users are aware boot CPU is not NO_HZ_FULL Frederic Weisbecker
2014-02-27 12:17 ` [GIT PULL] timers update for 3.15 Ingo Molnar
2014-02-27 12:53   ` Frederic Weisbecker [this message]

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=20140227125306.GA17608@localhost.localdomain \
    --to=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=viresh.kumar@linaro.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 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.