This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH 08/14] Add manual for lock elision
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Andi Kleen <andi at firstfloor dot org>
- Cc: libc-alpha at sourceware dot org, Andi Kleen <ak at linux dot jf dot intel dot com>
- Date: Fri, 28 Jun 2013 13:34:02 -0400
- Subject: Re: [PATCH 08/14] Add manual for lock elision
- References: <1372398717-16530-1-git-send-email-andi at firstfloor dot org> <1372398717-16530-9-git-send-email-andi at firstfloor dot org> <51CD44B5 dot 5000202 at redhat dot com> <20130628145037 dot GU6123 at two dot firstfloor dot org> <51CDC3FF dot 9050101 at redhat dot com> <20130628172137 dot GY6123 at two dot firstfloor dot org>
On 06/28/2013 01:21 PM, Andi Kleen wrote:
> On Fri, Jun 28, 2013 at 01:12:31PM -0400, Carlos O'Donell wrote:
>> On 06/28/2013 10:50 AM, Andi Kleen wrote:
>>> On Fri, Jun 28, 2013 at 04:09:25AM -0400, Carlos O'Donell wrote:
>>>> On 06/28/2013 01:51 AM, Andi Kleen wrote:
>>>>> From: Andi Kleen <ak@linux.intel.com>
>>>>>
>>>>> pthreads are not described in the documentation, but I decided to document
>>>>> lock elision there at least.
>>>>
>>>> Can we please split this into two manual patches?
>>>
>>> No, the constants conflicts with the environment patches are already a
>>> nightmare. If that's a requirement I'll rather remove most of the manual.
>>
>> I don't mind doing the work here.
>
> The problem is I have to fix the conflicts with the environment
> variable patch all the time, every time you make me change
> something (and you make me change something all the time)
>
>>
>> If you want I can checkin a minimal documentation patch.
>
> The state without the tuning interfaces should be on only
> very temporary (a few days I hope). So it can survive without manual
> I think.
If it's temporary then you shouldn't mind if we checkin
a temporary manual patch that ensures we have something
in place for 2.18?
I would really like the state of master to be consistent
and complete with respect to the baseline feature support
we're putting into it.
Cheers,
Carlos.