This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [RFC] Lock elision implementation guidelines
- From: Markus Trippelsdorf <markus at trippelsdorf dot de>
- To: Andi Kleen <ak at linux dot jf dot intel dot com>
- Cc: Torvald Riegel <triegel at redhat dot com>, GLIBC Devel <libc-alpha at sourceware dot org>, andi <andi at firstfloor dot org>
- Date: Fri, 7 Jun 2013 18:37:11 +0200
- Subject: Re: [RFC] Lock elision implementation guidelines
- References: <1360527652 dot 3065 dot 11521 dot camel at triegel dot csb> <1370618459 dot 16968 dot 11300 dot camel at triegel dot csb> <20130607162912 dot GD27861 at tassilo dot jf dot intel dot com>
On 2013.06.07 at 09:29 -0700, Andi Kleen wrote:
> On Fri, Jun 07, 2013 at 05:20:59PM +0200, Torvald Riegel wrote:
> > I've put those guidelines up as a page on the wiki:
> > http://sourceware.org/glibc/wiki/LockElisionGuide
> >
> > I incorporated the comments that came up in the discussion, and tried to
> > represent the results of this discussion. Please speak up if there are
> > points you disagree with.
>
> I don't see much sense to write such a guide out of theoretical considerations.
> Any practical guide needs to be based on experience.
> Many aspects of lock elision can be non intuitive and need validation on
> real systems.
>
> Please play around with the implementation, test it with your favourite
> applications and then write something up.
BTW, now that Haswell is released: Could you post some performance
numbers for your patchkit?
--
Markus