From: Ingo Molnar <mingo@kernel.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: peterz@infradead.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [GIT PULL rcu/next] Additional RCU commit for 3.15
Date: Tue, 25 Mar 2014 06:48:45 +0100 [thread overview]
Message-ID: <20140325054845.GA27206@gmail.com> (raw)
In-Reply-To: <20140325041638.GA23624@linux.vnet.ibm.com>
* Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
> Hello, Ingo,
>
> And, if you are willing to take it, one late-breaking commit. This one
> was requested for 3.15 by Peter Zijlstra. [...]
No objections at all, looks like a useful facility!
> [...] It is low risk because it adds a new in-kernel API with
> minimal changes to the existing code. Those minimal changes are the
> addition of memory barriers and ACCESS_ONCE() macro calls, neither
> of which should be able to break things. This commit has passed
> significant rcutorture testing, with these additional additions to
> rcutorture slated for 3.16. This commit has also been exposed to
> -next testing.
>
> This change is available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next
>
> for you to fetch changes up to 765a3f4fed708ae429ee095914a7897acb3a65bd:
>
> rcu: Provide grace-period piggybacking API (2014-03-20 17:12:25 -0700)
>
> ----------------------------------------------------------------
> Paul E. McKenney (1):
> rcu: Provide grace-period piggybacking API
>
> include/linux/rcutiny.h | 10 ++++++++
> include/linux/rcutree.h | 2 ++
> kernel/rcu/tree.c | 62 +++++++++++++++++++++++++++++++++++++++++++++----
> 3 files changed, 70 insertions(+), 4 deletions(-)
Pulled, thanks a lot Paul!
Ingo
prev parent reply other threads:[~2014-03-25 5:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 4:16 [GIT PULL rcu/next] Additional RCU commit for 3.15 Paul E. McKenney
2014-03-25 5:48 ` 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=20140325054845.GA27206@gmail.com \
--to=mingo@kernel.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.