From: Frederic Weisbecker <fweisbec@gmail.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>, Kevin Hilman <khilman@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>, Jens Axboe <axboe@fb.com>
Subject: Re: [PATCH 0/2] nohz: Move nohz kick out of scheduler IPI v2
Date: Thu, 3 Apr 2014 02:18:26 +0200 [thread overview]
Message-ID: <20140403001825.GC23338@localhost.localdomain> (raw)
In-Reply-To: <1396483767-28607-1-git-send-email-fweisbec@gmail.com>
Sorry I got Jens address wrong once again :-(
On Thu, Apr 03, 2014 at 02:09:25AM +0200, Frederic Weisbecker wrote:
> Hi Paul,
>
> Here's an updated version of the patches with your review addressed.
> I ripped the function parameter and let it be setup on queued IPI object
> initialization time so that people don't get confused and always use the
> same function for a given queued object.
>
> Please tell me if you find other issues.
>
> Thanks.
>
> 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(-)
>
> --
> 1.8.3.1
>
next prev parent reply other threads:[~2014-04-03 0:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 0:09 Frederic Weisbecker
2014-04-03 0:09 ` [PATCH 1/2] smp: Non busy-waiting IPI queue Frederic Weisbecker
2014-04-03 0:09 ` [PATCH 2/2] nohz: Move full nohz kick to its own IPI Frederic Weisbecker
2014-04-03 0:18 ` Frederic Weisbecker [this message]
2014-04-03 15:38 ` [PATCH 0/2] nohz: Move nohz kick out of scheduler IPI v2 Paul E. McKenney
2014-04-03 15:43 ` Frederic Weisbecker
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=20140403001825.GC23338@localhost.localdomain \
--to=fweisbec@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@fb.com \
--cc=khilman@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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
Powered by JetHome