X-Git-Url: https://git.liburcu.org/?a=blobdiff_plain;f=README;h=2d29c1d4e1c670800ec808a693f41cca2344ea0c;hb=07bd1a22e2ae42578d2a1854de8430cd1af13227;hp=9d154c53832d471871f99ca0e4dc1ae5ec74109f;hpb=1eade46a854eb8211be9fd32e0cf6835576deb63;p=urcu.git

diff --git a/README b/README
index 9d154c5..2d29c1d 100644
--- a/README
+++ b/README
@@ -17,7 +17,7 @@ BUILDING
 		* CFLAGS="-m64 -g -O2" ./configure
 
 		Forcing a 32-bit build with 386 backward compatibility:
-		* CFLAGS="-m32 -g -O2" ./configure --target=i386-pc-linux-gnu
+		* CFLAGS="-m32 -g -O2" ./configure --host=i386-pc-linux-gnu
 
 		Forcing a 32-bit build for Sparcv9 (typical for Sparc v9)
 		* CFLAGS="-m32 -Wa,-Av9a -g -O2" ./configure
@@ -273,4 +273,24 @@ Interaction with fork()
 	must invoke call_rcu_before_fork() before the fork() and
 	call_rcu_after_fork_parent() after the fork().  The child
 	process must invoke call_rcu_after_fork_child().
-	These three APIs are suitable for passing to pthread_atfork().
+	Even though these three APIs are suitable for passing to
+	pthread_atfork(), use of pthread_atfork() is *STRONGLY
+	DISCOURAGED* for programs calling the glibc memory allocator
+	(malloc(), calloc(), free(), ...) within call_rcu callbacks.
+	This is due to limitations in the way glibc memory allocator
+	handles calls to the memory allocator from concurrent threads
+	while the pthread_atfork() handlers are executing.
+	Combining e.g.:
+	* call to free() from callbacks executed within call_rcu worker
+	  threads,
+	* executing call_rcu atfork handlers within the glibc pthread
+	  atfork mechanism,
+	will sometimes trigger interesting process hangs. This usually
+	hangs on a memory allocator lock within glibc.
+
+Thread Local Storage (TLS)
+
+	Userspace RCU can fall back on pthread_getspecific() to emulate
+	TLS variables on systems where it is not available. This behavior
+	can be forced by specifying --disable-compiler-tls as configure
+	argument.