Threading libraries

Hasso Tepper hasso at
Sat Dec 13 00:50:59 PST 2008

Although having two threading libraries and nice runtime switching 
mechanism between them is nice, there is a problem. If something new 
needs to be implemented in threading library, it needs to be implemented 
in both of them. Even more, there is many functions (most notably 
barriers) implemented in libthread_xu, but not in libc_r making them 
actually unusable.

There is no changes since then except pthread_atfork and I don't see 
anyone working on more either.

I don't think that it's acceptable in long term, so either someone jumps 
in to implement missing stuff in libc_r or we should remove libc_r at all 
(at least in sense of

Any thoughts?

Hasso Tepper

More information about the Kernel mailing list