From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Alessio Igor Bogani <abogani@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Avi Kivity <avi@redhat.com>, Chris Metcalf <cmetcalf@tilera.com>,
Christoph Lameter <cl@linux.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Geoff Levand <geoff@infradead.org>,
Gilad Ben Yossef <gilad@benyossef.com>,
Hakan Akkan <hakanakkan@gmail.com>, Kevin Hilman <khilman@ti.com>,
Max Krasnyansky <maxk@qualcomm.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
Stephen Hemminger <shemminger@vyatta.com>,
Steven Rostedt <rostedt@goodmis.org>,
Sven-Thorsten Dietrich <thebigcorporation@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: [GIT PULL] nohz: Generalize nohz APIs for adaptive tickless
Date: Mon, 11 Jun 2012 18:53:17 +0200 [thread overview]
Message-ID: <1339433602-26836-1-git-send-email-fweisbec@gmail.com> (raw)
Ingo,
As per your suggestion I think it may be time to start a tree in -tip
and iterate incrementally there with what looks to me like the
uncontroversial bits of nohz cpusets.
This pile does the preparatory work to make the nohz API idle-agnostic
so that we are able to stop and restart the tick from non-idle places.
If you're fine with it, it's pullable there:
git://github.com/fweisbec/linux-dynticks.git
nohz-for-tip
Frederic Weisbecker (5):
nohz: Separate idle sleeping time accounting from nohz logic
nohz: Make nohz API agnostic against idle ticks cputime accounting
nohz: Rename ts->idle_tick to ts->last_tick
nohz: Move ts->idle_calls incrementation into strict idle logic
nohz: Move next idle expiry time record into idle logic area
include/linux/tick.h | 8 +-
kernel/time/tick-sched.c | 191 ++++++++++++++++++++++++++--------------------
kernel/time/timer_list.c | 4 +-
3 files changed, 115 insertions(+), 88 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-06-11 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 16:53 Frederic Weisbecker [this message]
2012-06-11 16:53 ` [PATCH 1/5] nohz: Separate idle sleeping time accounting from nohz logic Frederic Weisbecker
2012-06-11 18:09 ` Frederic Weisbecker
2012-06-11 16:53 ` [PATCH 2/5] nohz: Make nohz API agnostic against idle ticks cputime accounting Frederic Weisbecker
2012-06-11 16:53 ` [PATCH 3/5] nohz: Rename ts->idle_tick to ts->last_tick Frederic Weisbecker
2012-06-11 16:53 ` [PATCH 4/5] nohz: Move ts->idle_calls incrementation into strict idle logic Frederic Weisbecker
2012-06-11 16:53 ` [PATCH 5/5] nohz: Move next idle expiry time record into idle logic area 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=1339433602-26836-1-git-send-email-fweisbec@gmail.com \
--to=fweisbec@gmail.com \
--cc=abogani@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=cl@linux.com \
--cc=cmetcalf@tilera.com \
--cc=daniel.lezcano@linaro.org \
--cc=geoff@infradead.org \
--cc=gilad@benyossef.com \
--cc=hakanakkan@gmail.com \
--cc=khilman@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=shemminger@vyatta.com \
--cc=tglx@linutronix.de \
--cc=thebigcorporation@gmail.com \
/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
all inboxes | Powered by JetHome®