[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140604103003.GE11096@twins.programming.kicks-ass.net>
Date: Wed, 4 Jun 2014 12:30:03 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Davidlohr Bueso <davidlohr@...com>
Cc: Ingo Molnar <mingo@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel@...r.kernel.org,
"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, Jun 03, 2014 at 02:50:51PM -0700, Davidlohr Bueso wrote:
> 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?
Ingo is 'missing' most of the time, so while I sit here with a massive
queue of patches its nearly impossible for me to get anything merged :-(
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists