[M3devel] userthreads vs. pthreads performance?

Mika Nystrom mika at async.async.caltech.edu
Sun Mar 28 20:57:40 CEST 2010


Yep, sounds right.  

I was profiling some other thread-using code that slowed down enormously
because of pthreads and it turned out the program was spending ~95%
of its time in accessing the thread locals via one of the pthread_ functions.
(The overhead of entering the kernel.)

   Mika

=?UTF-8?Q?Dragi=C5=A1a_Duri=C4=87?= writes:
>Fast glance shows there is no overhead in code? Just passthrough of
>MUTEX field to pthread_mutex_lock()? And inefficiency comes from there?
>
>On Sun, 2010-03-28 at 12:55 -0400, Tony Hosking wrote:
>> Yes, we need to implement thin locks and biased locks.  These have
>> minimal overhead for locks held mostly by just one thread.
>-- 
>Dragiša Durić <dragisha at m3w.org>



More information about the M3devel mailing list