[M3devel] lock performance, random thoughts

[Jay K]

uncontended pthread_mutex_lock/unlock:

  syscall on FreeBSD? Solaris? NetBSD? Darwin?

  Not on Linux.

  I really doubt on Solaris.

 

Ditto pthread_self, pthread_getspecific, pthread_setspecific?

(Though I don't believe we call them frequently on Solaris, and I have a very rough plan to reduce them *later* -- libunwind.)

 

 - Jay

> From: dragisha at m3w.org
> To: Highjinks at gmx.com
> Date: Thu, 8 Apr 2010 00:06:29 +0200
> CC: m3devel at elegosoft.com
> Subject: Re: [M3devel] lock performance, random thoughts
> 
> It's all about synchronization in kernel space, ie part of it when it
> comes to kernel space through syscalls.
> 
> Context switching is lesser problem as it is what happens a lot less
> often than synchronization.
> 
> Synchronization problem is with systems which are, unlike Linux, doing
> syscalls on every pthread_mutex_lock and friends.
> 
> Hybridization of thread system (mixing user and kernel threads) is done
> talk and I hope nobody takes such thing seriously anymore.
> 
> On Wed, 2010-04-07 at 22:09 +0200, Chris wrote:
> > As I've said before, this really has NOTHING to do with user/kernel
> > level threading. It's all about synchronization.
> -- 
> Dragiša Durić <dragisha at m3w.org>
> 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20100408/8259e104/attachment-0002.html>