[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1401832251.8843.3.camel@buesod1.americas.hpqcorp.net>
Date: Tue, 03 Jun 2014 14:50:51 -0700
From: Davidlohr Bueso <davidlohr@...com>
To: Ingo Molnar <mingo@...nel.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel@...r.kernel.org,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
"Paul E. McKenney" <paulmck@...ibm.com>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] locking tree changes for v3.16
On Tue, 2014-06-03 at 13:48 +0200, Ingo Molnar wrote:
> Linus,
>
> Please pull the latest locking-core-for-linus git tree from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking-core-for-linus
>
> # HEAD: 3cf2f34e1a3d4d5ff209d087925cf950e52f4805 rwsem: Add comments to explain the meaning of the rwsem's count field
>
> 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).
Also curious about why Peter's rewrite of the qrwlock_t was removed from
-tip... I noticed it was there for a few days then disappeared. What am
I missing?
Thanks,
Davidlohr
--
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