[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140227125306.GA17608@localhost.localdomain>
Date: Thu, 27 Feb 2014 13:53:09 +0100
From: Frederic Weisbecker <fweisbec@...il.com>
To: Ingo Molnar <mingo@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Peter Zijlstra <peterz@...radead.org>,
Steven Rostedt <rostedt@...dmis.org>,
Thomas Gleixner <tglx@...utronix.de>,
Viresh Kumar <viresh.kumar@...aro.org>
Subject: Re: [GIT PULL] timers update for 3.15
On Thu, Feb 27, 2014 at 01:17:07PM +0100, Ingo Molnar wrote:
>
> * Frederic Weisbecker <fweisbec@...il.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 ;)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists