X-Git-Url: https://git.liburcu.org/?a=blobdiff_plain;f=README;h=1cd3ed954fbd780e83fab12a6fe85f960e84ae95;hb=79266051c59604c3923944d8003f8a9d2ad3c08b;hp=b3839e1a614a134c4960cc96824cefca83078d69;hpb=fdf01eeda9f634a32db3fc90cd342da08d7a259d;p=urcu.git

diff --git a/README b/README
index b3839e1..1cd3ed9 100644
--- a/README
+++ b/README
@@ -28,6 +28,9 @@ Currently, x86 (i386, i486, i586, i686), x86 64-bit, PowerPC 32/64, S390, S390x
 and Sparcv9 32/64 are supported. Only tested on Linux so far, but should
 theoretically work on other operating systems.
 
+Alpha and ia64 architectures are supported, but depend on 4.x gcc with atomic
+builtins support.
+
 QUICK START GUIDE
 -----------------
 
@@ -71,7 +74,8 @@ Usage of liburcu-mb
 
 Usage of liburcu-signal
 
-	* #include <urcu-signal.h>
+	* #include <urcu.h>
+	* Compile any _LGPL_SOURCE code using this library with "-DRCU_SIGNAL".
 	* Link the application with "-lurcu-signal".
 	* Version of the library that requires a signal, typically SIGUSR1. Can
 	  be overridden with -DSIGRCU by modifying Makefile.build.inc.
@@ -146,6 +150,14 @@ Being careful with signals
 	rcu_quiescent_state() calls, when threads are put offline and around
 	calls to synchronize_rcu(). Even then, we do not recommend it.
 
+Interaction with mutexes
+
+	One must be careful to do not cause deadlocks due to interaction of
+	synchronize_rcu() and RCU read-side with mutexes. If synchronize_rcu()
+	is called with a mutex held, this mutex (or any mutex which has this
+	mutex in its dependency chain) should not be acquired from within a RCU
+	read-side critical section.
+
 Usage of DEBUG_RCU
 
 	DEBUG_RCU is used to add internal debugging self-checks to the