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: TSX lock elision for glibc v2

From: Andi Kleen <andi at firstfloor dot org>
To: Torvald Riegel <triegel at redhat dot com>
Cc: Andi Kleen <andi at firstfloor dot org>, libc-alpha at sourceware dot org
Date: Sat, 19 Jan 2013 00:38:55 +0100
Subject: Re: TSX lock elision for glibc v2
References: <1357849182-21257-1-git-send-email-andi@firstfloor.org> <1357925555.3375.24950.camel@triegel.csb> <20130111174120.GK30577@one.firstfloor.org> <1357939708.3375.25889.camel@triegel.csb> <20130111222900.GM30577@one.firstfloor.org> <1358360179.3375.30105.camel@triegel.csb> <m2vcaxyo8k.fsf@firstfloor.org> <1358506817.25369.910.camel@triegel.csb>

Sorry the question doesn't make any sense to me and I cannot
answer it. If you think the read write lock elision should
do something different please present a code example.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.

Follow-Ups:
- Re: TSX lock elision for glibc v2
  - From: Torvald Riegel

References:
- TSX lock elision for glibc v2
  - From: Andi Kleen
- Re: TSX lock elision for glibc v2
  - From: Torvald Riegel
- Re: TSX lock elision for glibc v2
  - From: Andi Kleen
- Re: TSX lock elision for glibc v2
  - From: Torvald Riegel
- Re: TSX lock elision for glibc v2
  - From: Andi Kleen
- Re: TSX lock elision for glibc v2
  - From: Torvald Riegel
- Re: TSX lock elision for glibc v2
  - From: Andi Kleen
- Re: TSX lock elision for glibc v2
  - From: Torvald Riegel

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