|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] pthread_mutex_lock() and Xenstored
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
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] pthread_mutex_lock() and Xenstored,
Peter Teoh <=
|
|
|
|
|