X-Git-Url: http://git.liburcu.org/?a=blobdiff_plain;f=README;h=81afe0e2757c8bceabef7c50ff4102d0600aa8d3;hb=f4b7d3c9a033944b3a20c32a416cb9c7506a37d3;hp=33038af3ab12c0cc96aacbedf3cf6e76ea2fd5f7;hpb=aac98a5504a989c227bb9290f2849abc9458811c;p=urcu.git

diff --git a/README b/README
index 33038af..81afe0e 100644
--- a/README
+++ b/README
@@ -22,6 +22,7 @@ BUILDING
 		Forcing a 32-bit build for Sparcv9 (typical for Sparc v9)
 		* CFLAGS="-m32 -Wa,-Av9a -g -O2" ./configure
 
+
 ARCHITECTURES SUPPORTED
 -----------------------
 
@@ -66,6 +67,19 @@ Test scripts provided in the tests/ directory of the source tree depend
 on "bash" and the "seq" program.
 
 
+API
+---
+
+See the relevant API documentation files in doc/. The APIs provided by
+Userspace RCU are, by prefix:
+
+- rcu_ : Read-Copy Update
+- cmm_ : Concurrent Memory Model
+- caa_ : Concurrent Architecture Abstraction
+- cds_ : Concurrent Data Structures
+- uatomic_: Userspace Atomic
+
+
 QUICK START GUIDE
 -----------------
 
@@ -189,11 +203,12 @@ Being careful with signals
 	signal(7). The liburcu-mb and liburcu-qsbr versions of the Userspace RCU
 	library do not require any signal.
 
-	Read-side critical sections are allowed in a signal handler with
-	liburcu and liburcu-mb. Be careful, however, to disable these signals
+	Read-side critical sections are allowed in a signal handler,
+	except those setup with sigaltstack(2), with liburcu and
+	liburcu-mb. Be careful, however, to disable these signals
 	between thread creation and calls to rcu_register_thread(), because a
-	signal handler nesting on an unregistered thread would not be allowed to
-	call rcu_read_lock().
+	signal handler nesting on an unregistered thread would not be
+	allowed to call rcu_read_lock().
 
 	Read-side critical sections are _not_ allowed in a signal handler with
 	liburcu-qsbr, unless signals are disabled explicitly around each