Re: [GIT PULL] locking tree changes for v3.16
From: Ingo Molnar
Date: Thu Jun 05 2014 - 04:18:20 EST
* Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote:
> 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?
I merged it, but then it broke and I reported the breakage - and
zapped the bits to not create dependencies on broken bits.
( There was also quite some discussion back and forth as recently as
two weeks ago, so it didn't feel cooked enough to me to pick it up
directly from email - but once it shows up in your queue I'm picking
it up. )
> 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 :-(
Right now I'm somewhat 'missing' because I fell ill right when the
merge window began :-/ But I merged all your pending bits shortly
before the merge window started. During the merge window itself I
try not to merge fresh patches.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/