This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: TSX lock elision for glibc v12
- From: Andi Kleen <andi at firstfloor dot org>
- To: Torvald Riegel <triegel at redhat dot com>
- Cc: Andi Kleen <andi at firstfloor dot org>, Rich Felker <dalias at aerifal dot cx>, libc-alpha at sourceware dot org, Carlos O'Donell <carlos at redhat dot com>, Roland McGrath <roland at hack dot frob dot com>
- Date: Fri, 21 Jun 2013 19:27:01 +0200
- Subject: Re: TSX lock elision for glibc v12
- References: <1371592286-22073-1-git-send-email-andi at firstfloor dot org> <1371753271 dot 964 dot 2220 dot camel at triegel dot csb> <20130621012328 dot GA29800 at brightrain dot aerifal dot cx> <1371811686 dot 964 dot 4100 dot camel at triegel dot csb> <1371823366 dot 964 dot 4706 dot camel at triegel dot csb> <1371824261 dot 964 dot 4757 dot camel at triegel dot csb> <1371826829 dot 964 dot 4905 dot camel at triegel dot csb> <20130621160924 dot GN6123 at two dot firstfloor dot org> <1371833629 dot 964 dot 5253 dot camel at triegel dot csb>
> I don't want to change or expose anything externally if I don't have to.
> This will make it easier for us to just enable elision without risking
> to have to maintain other interfaces, break ABIs, etc.
I don't see the point of checking a new number on all the fast paths
when it doesn't do anything different.
With elision it's just the same as TIMED_NP | NO_ELISION
So why not use that internally?
I also found flags in general more efficient to handle than new types.
-Andi