From: Andrew Morton <akpm@linux-foundation.org>
To: Davidlohr Bueso <davidlohr@hp.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
"Paul E. McKenney" <paulmck@us.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [GIT PULL] locking tree changes for v3.16
Date: Tue, 3 Jun 2014 14:55:26 -0700 [thread overview]
Message-ID: <20140603145526.f78e1cb7462048376709b6f0@linux-foundation.org> (raw)
In-Reply-To: <1401832251.8843.3.camel@buesod1.americas.hpqcorp.net>
On Tue, 03 Jun 2014 14:50:51 -0700 Davidlohr Bueso <davidlohr@hp.com> wrote:
> > The main changes in this cycle were:
> >
> > - reduced/streamlined smp_mb__*() interface that allows more usecases
> > and makes the existing ones less buggy, especially in rarer
> > architectures
> >
> > - add rwsem implementation comments
> >
> > - bump up lockdep limits
>
> So I guess the rwsem optimistic spinning stuff will be routed through
> akpm then (which is already in -next for a while, through -mm).
I'd prefer not - I put it in there just to get some linux-next exposure.
A change like this should be carefully poked at by people who understand
what they're poking.
next prev parent reply other threads:[~2014-06-03 21:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 11:48 Ingo Molnar
2014-06-03 21:50 ` Davidlohr Bueso
2014-06-03 21:55 ` Andrew Morton [this message]
2014-06-03 22:02 ` Davidlohr Bueso
2014-06-03 22:53 ` Andrew Morton
2014-06-04 10:30 ` Peter Zijlstra
2014-06-04 16:17 ` Linus Torvalds
2014-06-04 17:22 ` Peter Zijlstra
2014-06-04 21:22 ` Linus Torvalds
2014-06-04 21:35 ` Thomas Gleixner
2014-06-05 1:22 ` Davidlohr Bueso
2014-06-05 8:19 ` Ingo Molnar
2014-06-05 8:22 ` Thomas Gleixner
2014-06-05 8:29 ` Ingo Molnar
2014-06-05 8:17 ` Ingo Molnar
2014-06-05 9:21 ` Peter Zijlstra
2014-06-05 9:24 ` Ingo Molnar
2014-06-05 11:11 ` Ingo Molnar
2014-06-05 11:20 ` Ingo Molnar
2014-06-05 12:27 ` Peter Zijlstra
2014-06-05 12:35 ` Ingo Molnar
2014-06-05 12:41 ` Peter Zijlstra
2014-06-05 12:47 ` Ingo Molnar
2014-06-05 12:53 ` Peter Zijlstra
2014-06-05 13:13 ` Peter Zijlstra
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=20140603145526.f78e1cb7462048376709b6f0@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=davidlohr@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@us.ibm.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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®