[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] pthread_mutex_lock() and Xenstored


  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
  • Date: Fri, 31 Aug 2007 13:51:18 +0800
  • Delivery-date: Thu, 13 Sep 2007 05:26:07 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:to:subject:date:mime-version:content-type:x-priority:x-msmail-priority:x-mailer:x-mimeole:from; b=Wa2at2JM+KgzzIIVdfw7YmxEyBqkgnNKiHbzTJUxwMZsWgDDMxn4qZJ9KaJUX/xkA9Kiylp51KM8Y/bnCQN6EuNkGhtwPyAWYp33rIUoiyy5toe0Xz/LoO9Evjdykm/6ThsLUtKXxja/KJdS0JtOGCosHchJ9fWelRrIzrRSCeU=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

pthread_mutex_lock() are not async-signal safe (ref:
but I still see that it is used extensively in xenstored implementation (eg, xs.c).
 
Moreover, pthread_mutex_lock() suffered a higher performance penalty than other synchronization option.   For a one-time effort like domain creation this is ok, but Xenstore is used repeatedly to access data, and therefore performance could potentially be enhanced.
 
Does all these sound logical?
 
 
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.