From: Ingo Molnar <mingo@kernel.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
josh@joshtriplett.org, niv@us.ibm.com, tglx@linutronix.de,
peterz@infradead.org, rostedt@goodmis.org,
Valdis.Kletnieks@vt.edu, dhowells@redhat.com,
eric.dumazet@gmail.com, darren@dvhart.com, fweisbec@gmail.com,
patches@linaro.org
Subject: Re: [PATCH tip/core/rcu 0/7] RCU_FAST_NO_HZ changes for 3.6
Date: Fri, 8 Jun 2012 11:04:17 +0200 [thread overview]
Message-ID: <20120608090417.GA10841@gmail.com> (raw)
In-Reply-To: <20120608042632.GA1250@linux.vnet.ibm.com>
* Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
> Hello!
>
> This patch series provides more adjustments to the (relatively) new
> large-system-safe implementation for RCU_FAST_NO_HZ:
>
> 1. Remove RCU_FAST_NO_HZ dependency on stop_machine() nature of
> CPU hotplug.
> 2. Make RCU_FAST_NO_HZ tracing distinguish between short and
> long idle intervals.
> 3. Move RCU_FAST_NO_HZ per-CPU state variables to the rcu_dynticks
> per-CPU structure.
> 4. Precompute RCU_FAST_NO_HZ timer offsets so that the timers
> will actually be paid attention to. This fixes the slow-boot
> problem that hit a few people.
> 5. Convert ftrace_dump() calls in idle entry and idle exit from
> DUMP_ALL to DUMP_ORIG.
> 6. Fix erroneous TINY_PREEMPT_RCU assumption that rcu_preempt_needs_cpu()
> is a quiescent state (it is not).
> 7. Round RCU_FAST_NO_HZ lazy timeout to nearest second to conserve
> power on systems with synchronized scheduler-clock interrupts.
>
> I am considering pushing #1-#4 into 3.5 for the slow-boot regression.
> If you object, please let me know.
Sure, that's sensible - could get this to me ASAP so that we can
send it to Linus before -rc2? #3 and #4 are pretty large so we
want them upstream ASAP.
Thanks,
Ingo
prev parent reply other threads:[~2012-06-08 9:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 4:26 [PATCH tip/core/rcu 0/7] RCU_FAST_NO_HZ changes for 3.6 Paul E. McKenney
2012-06-08 4:26 ` [PATCH rcu 1/8] rcu: RCU_FAST_NO_HZ detection of callback adoption Paul E. McKenney
2012-06-08 4:26 ` [PATCH rcu 2/8] rcu: Update RCU_FAST_NO_HZ tracing for lazy callbacks Paul E. McKenney
2012-06-08 4:26 ` [PATCH rcu 3/8] rcu: Move RCU_FAST_NO_HZ per-CPU variables to rcu_dynticks structure Paul E. McKenney
2012-06-08 4:26 ` [PATCH rcu 4/8] rcu: Precompute RCU_FAST_NO_HZ timer offsets Paul E. McKenney
2012-06-08 4:26 ` [PATCH rcu 5/8] rcu: Dump only the current CPU's buffers for idle-entry/exit warnings Paul E. McKenney
2012-06-08 4:26 ` [PATCH rcu 6/8] rcu: The rcu_needs_cpu() function is not a quiescent state Paul E. McKenney
2012-06-08 4:26 ` [PATCH rcu 7/8] rcu: Round FAST_NO_HZ lazy timeout to nearest second Paul E. McKenney
2012-06-08 4:26 ` [PATCH rcu 8/8] rcu: Fix qlen_lazy breakage Paul E. McKenney
2012-06-08 9:04 ` 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=20120608090417.GA10841@gmail.com \
--to=mingo@kernel.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=darren@dvhart.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=eric.dumazet@gmail.com \
--cc=fweisbec@gmail.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@elte.hu \
--cc=niv@us.ibm.com \
--cc=patches@linaro.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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