[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120228095132.GA16511@elte.hu>
Date: Tue, 28 Feb 2012 10:51:32 +0100
From: Ingo Molnar <mingo@...e.hu>
To: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc: linux-kernel@...r.kernel.org, fweisbec@...il.com,
rostedt@...dmis.org, schwidefsky@...ibm.com,
heiko.carstens@...ibm.com, nab@...ux-iscsi.org, jkosina@...e.cz,
jj@...osbits.net, davem@...emloft.net, linville@...driver.com,
johannes@...solutions.net, josh@...htriplett.org,
a.p.zijlstra@...llo.nl, dhowells@...hat.com, Julia.Lawall@...6.fr,
deepthi@...ux.vnet.ibm.com, neven.m.abou.gazala@...el.com,
hughd@...gle.com
Subject: Re: [GIT PULL rcu/next] RCU commits for 3.4
* Paul E. McKenney <paulmck@...ux.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists