From: Ingo Molnar <mingo@kernel.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Kevin Hilman <khilman@linaro.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Viresh Kumar <viresh.kumar@linaro.org>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [GIT PULL] nohz: Move nohz kick out of scheduler IPI, v9
Date: Wed, 18 Jun 2014 18:48:41 +0200 [thread overview]
Message-ID: <20140618164841.GA19204@gmail.com> (raw)
In-Reply-To: <1402935790-19860-1-git-send-email-fweisbec@gmail.com>
* Frederic Weisbecker <fweisbec@gmail.com> wrote:
> Ingo,
>
> Please pull the timers/nohz-irq-work-v7 branch that can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> timers/nohz-irq-work-v7
>
> It has been acked by Peterz.
>
> --- Summary ---
>
> This set moves the nohz kick, used to notify a full dynticks CPU when
> events require tick rescheduling, out of the scheduler tick to a
> dedicated IPI.
>
> This debloats a bit the scheduler IPI from off-topic work that was
> abusing that scheduler fast path for its convenient asynchronous
> properties. Now the nohz kick uses irq work for its own needs.
>
> Of course this implied quite some background infrastructure rework,
> including:
>
> * Clean up some irq work internals
> * Implement remote irq work
> * Implement nohz kick on top of remote irq work
> * Move full dynticks timer enqueue notification to new kick
> * Move multi-task notification to new kick
> * Remove unecessary barriers on multi-task notification
>
> Thanks,
> Frederic
> ---
>
> Frederic Weisbecker (6):
> irq_work: Split raised and lazy lists
> irq_work: Implement remote queueing
> nohz: Support nohz full remote kick
> nohz: Switch to nohz full remote kick on timer enqueue
> nohz: Use nohz own full kick on 2nd task enqueue
> nohz: Use IPI implicit full barrier against rq->nr_running r/w
>
>
> include/linux/irq_work.h | 5 ++++
> include/linux/tick.h | 9 +++++-
> kernel/irq_work.c | 76 ++++++++++++++++++++++++++++++------------------
> kernel/sched/core.c | 22 ++++++++------
> kernel/sched/sched.h | 12 ++++++--
> kernel/smp.c | 9 ++++++
> kernel/time/tick-sched.c | 10 ++++---
> 7 files changed, 97 insertions(+), 46 deletions(-)
Pulled, thanks a lot Frederic!
Ingo
next prev parent reply other threads:[~2014-06-18 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 16:23 [GIT PULL] nohz: Move nohz kick out of scheduler IPI, v9 Frederic Weisbecker
2014-06-18 16:48 ` Ingo Molnar [this message]
2014-06-23 12:53 ` Peter Zijlstra
2014-06-25 5:51 ` Ingo Molnar
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=20140618164841.GA19204@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=eric.dumazet@gmail.com \
--cc=fweisbec@gmail.com \
--cc=khilman@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox