WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] pthread_mutex_lock() and Xenstored

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] pthread_mutex_lock() and Xenstored
From: Peter Teoh <htmldeveloper@xxxxxxxxx>
Date: Fri, 31 Aug 2007 13:51:18 +0800
Delivery-date: Thu, 13 Sep 2007 05:26:07 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:to:subject:date:mime-version:content-type:x-priority:x-msmail-priority:x-mailer:x-mimeole:from; b=mNZZliGEu2y/lS8GdOncI67UEBpZL46A/8hMr9s33zwqF97/7p2B10TE8SxnhsMDewK5zf8wB3rsp/F+GvQSr1D1c3DyIu0Hg1CKvQDAl4BdvlZjRUbWTWZKXjNOZMAAvlxlG+/S+zCMCp+hDXvVmuGIG51mCiFB1mObwhPhkI0=
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=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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