From: Ingo Molnar <mingo@elte.hu>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, fweisbec@gmail.com,
rostedt@goodmis.org, schwidefsky@de.ibm.com,
heiko.carstens@de.ibm.com, nab@linux-iscsi.org, jkosina@suse.cz,
jj@chaosbits.net, davem@davemloft.net, linville@tuxdriver.com,
johannes@sipsolutions.net, josh@joshtriplett.org,
a.p.zijlstra@chello.nl, dhowells@redhat.com,
Julia.Lawall@lip6.fr, deepthi@linux.vnet.ibm.com,
neven.m.abou.gazala@intel.com, hughd@google.com
Subject: Re: [GIT PULL rcu/next] RCU commits for 3.4
Date: Tue, 28 Feb 2012 10:51:32 +0100 [thread overview]
Message-ID: <20120228095132.GA16511@elte.hu> (raw)
In-Reply-To: <20120227172248.GA5338@linux.vnet.ibm.com>
* Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
> Hello, Ingo,
>
> The major features of this series are making RCU more aggressive about
> entering dyntick-idle mode in order to improve energy efficiency,
> converting a few more call_rcu()s to kfree_rcu()s, applying a number
> of rcutree fixes and cleanups to rcutiny, removing CONFIG_SMP #ifdefs
> from treercu, allowing RCU CPU stall times to be set via sysfs, adding
> CPU-stall capability to rcutorture, adding more RCU-abuse diagnostics,
> updating documentation, and fixing yet more issue located in the
> still-ongoing top-to-bottom inspection of RCU, this time with a special
> focus on the CPU-hotplug code path.
I stuck this nice list into the merge commit, for future
generations.
> Three of the kfree_rcu() conversions have not yet received
> acks (s390, tcm_fc, and mac80211), but the maintainers have
> been CCed on multiple LKML postings and -next testing has not
> shown any problems.
>
> These commits have been posted to LKML (https://lkml.org/lkml/2012/2/3/459
> and https://lkml.org/lkml/2012/2/21/228) and have received -next testing.
> They are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next
Pulled, thanks a lot Paul!
Ingo
prev parent reply other threads:[~2012-02-28 9:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 17:22 [GIT PULL rcu/next] RCU commits for 3.4 Paul E. McKenney
2012-02-28 9:51 ` 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=20120228095132.GA16511@elte.hu \
--to=mingo@elte.hu \
--cc=Julia.Lawall@lip6.fr \
--cc=a.p.zijlstra@chello.nl \
--cc=davem@davemloft.net \
--cc=deepthi@linux.vnet.ibm.com \
--cc=dhowells@redhat.com \
--cc=fweisbec@gmail.com \
--cc=heiko.carstens@de.ibm.com \
--cc=hughd@google.com \
--cc=jj@chaosbits.net \
--cc=jkosina@suse.cz \
--cc=johannes@sipsolutions.net \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=nab@linux-iscsi.org \
--cc=neven.m.abou.gazala@intel.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=schwidefsky@de.ibm.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