This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [RFC] Lock elision implementation guidelines

From: Andi Kleen <ak at linux dot intel dot com>
To: Torvald Riegel <triegel at redhat dot com>
Cc: Rich Felker <dalias at aerifal dot cx>,GLIBC Devel <libc-alpha at sourceware dot org>, andi <andi at firstfloor dot org>
Date: Fri, 15 Feb 2013 09:25:00 -0800
Subject: Re: [RFC] Lock elision implementation guidelines
References: <1360527652.3065.11521.camel@triegel.csb><20130213001224.GZ20323@brightrain.aerifal.cx><1360928791.3065.18436.camel@triegel.csb>

> Andi, have you looked at option 1?  I know you can't discuss performance
> in detail, but perhaps you can add something to this discussion.

I don't consider it a realistic option for performance reasons.
The current abort preserves all semantics.

-Andi

References:
- [RFC] Lock elision implementation guidelines
  - From: Torvald Riegel
- Re: [RFC] Lock elision implementation guidelines
  - From: Rich Felker
- Re: [RFC] Lock elision implementation guidelines
  - From: Torvald Riegel

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]