From: Ingo Molnar <mingo@kernel.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jens Axboe <axboe@fb.com>, Kevin Hilman <khilman@linaro.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [GIT PULL v2] nohz: Move nohz kick out of scheduler IPI
Date: Wed, 16 Apr 2014 09:37:08 +0200 [thread overview]
Message-ID: <20140416073708.GA5636@gmail.com> (raw)
In-Reply-To: <1396541832-459-1-git-send-email-fweisbec@gmail.com>
* Frederic Weisbecker <fweisbec@gmail.com> wrote:
> Ingo, Thomas,
>
> Please pull the timers/nohz-ipi-for-tip-v3 branch that can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> timers/nohz-ipi-for-tip-v3
>
> It is based on 7a48837732f87a574ee3e1855927dc250117f565
> ("Merge branch 'for-3.15/core' of git://git.kernel.dk/linux-block")
> due to dependencies on the block tree containing IPI core changes.
>
> This v2 addresses Paul review and add his reviewed-by tags.
>
> I'm trying to get these 2 patches in before the merge window ends
> otherwise we'll have to do tricky branch split on the next cycle.
>
> ---
> When a full dynticks CPU runs in single task mode then a new task gets
> enqueued, we notify it through an IPI such that it restarts its tick.
>
> The IPI used here is the scheduler IPI. There are a few reasons for that:
> it can be called when interrupts are disabled, it can be called
> concurrently... These convenient properties altogether aren't yet offered
> by the IPI subsystem.
>
> Meanwhile, bloating that way the scheduler IPI with scheduler unrelated
> code is an abuse of this fast path. We certainly don't want to start a
> big kernel IPI.
>
> So this patchset adds a small helper to the IPI subsystem that allows
> to queue an IPI from interrupt disabled code while handling concurrent
> callers as well. Eventually the nohz kick gets converted to this new facility.
>
> Partly inspired by a suggestion from Peter Zijlstra.
>
> * Patch 1/2 brings the IPI infrastructure to support this
> * Patch 2/2 does the nohz IPI conversion
>
>
> Thanks,
> Frederic
> ---
>
> Frederic Weisbecker (2):
> smp: Non busy-waiting IPI queue
> nohz: Move full nohz kick to its own IPI
>
>
> include/linux/smp.h | 11 +++++++++++
> include/linux/tick.h | 2 ++
> kernel/sched/core.c | 5 +----
> kernel/sched/sched.h | 2 +-
> kernel/smp.c | 42 ++++++++++++++++++++++++++++++++++++++++++
> kernel/time/tick-sched.c | 21 +++++++++++++++++++++
> 6 files changed, 78 insertions(+), 5 deletions(-)
Pulled into tip:timers/nohz, thanks a lot Frederic!
Ingo
prev parent reply other threads:[~2014-04-16 7:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 16:17 [GIT PULL v2] nohz: Move nohz kick out of scheduler IPI Frederic Weisbecker
2014-04-03 16:17 ` [PATCH 1/2] smp: Non busy-waiting IPI queue Frederic Weisbecker
2014-04-03 16:17 ` [PATCH 2/2] nohz: Move full nohz kick to its own IPI Frederic Weisbecker
2014-04-09 15:28 ` [GIT PULL v2] nohz: Move nohz kick out of scheduler IPI Frederic Weisbecker
2014-04-14 11:22 ` Ingo Molnar
2014-04-14 23:04 ` Frederic Weisbecker
2014-04-15 6:05 ` Ingo Molnar
2014-04-16 7:37 ` Ingo Molnar [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=20140416073708.GA5636@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@fb.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 \
/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