This is the mail archive of the 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

On Tue, Jan 22, 2013 at 05:45:11PM +0100, Torvald Riegel wrote:
> On Sat, 2013-01-19 at 00:38 +0100, Andi Kleen wrote:
> > 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.
> No, the implementation you posted makes sense; I had just asked whether
> you had considered certain other lock elision uses too, and it seems as
> you haven't.  Which is fine -- I think we have enough other things to
> discuss.

I considered malloc and condition variables in the past.

But it's unclear if malloc would really benefit.  The new per thread
pool malloc seems to do reasonably well. 

Condition variables likely would benefit and I have some test cases that would
benefit.  But it wouldn't help always, only when not blocking.

I also considered stdio at some point, but it is unlikely to help there.

But first have to get the basics going, before thinking about those.
than glibc.  Baby steps are important.

In any case user applications tend to have far worse locking problems
than glibc.


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