X-Git-Url: https://git.liburcu.org/?a=blobdiff_plain;f=README;h=56e98d768e960ede0a80245a8a1a725218de33d4;hb=81ad2e193e8072f8246212d7eaba72769306c2e4;hp=4423fc53821c0c62244481cd8e94d8e4c837fc4f;hpb=3b38cfe1a3903f5d47af8b2745130af5a88a4bf6;p=urcu.git

diff --git a/README b/README
index 4423fc5..56e98d7 100644
--- a/README
+++ b/README
@@ -24,12 +24,11 @@ BUILDING
 ARCHITECTURES SUPPORTED
 -----------------------
 
-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.
+Currently, x86 (i386, i486, i586, i686), x86 64-bit, PowerPC 32/64, S390, S390x,
+ARM, Alpha, ia64 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.
+ARM depends on running a Linux kernel 2.6.15 or better.
 
 The gcc compiler versions 3.3, 3.4, 4.0, 4.1, 4.2, 4.3, 4.4 and 4.5 are
 supported, with the following exceptions:
@@ -39,6 +38,9 @@ supported, with the following exceptions:
   therefore not compatible with liburcu on x86 32-bit (i386, i486, i586, i686).
   The problem has been reported to the gcc community:
     http://www.mail-archive.com/gcc-bugs@gcc.gnu.org/msg281255.html
+- Alpha, ia64 and ARM architectures depend on 4.x gcc with atomic builtins
+  support.
+
 
 QUICK START GUIDE
 -----------------
@@ -188,3 +190,21 @@ SMP support
 		./configure --disable-smp-support
 
 	theoretically yielding slightly better performance.
+
+Interaction with fork()
+
+	Special care must be taken for applications performing fork() without
+	any following exec(). This is caused by the fact that Linux only clones
+	the thread calling fork(), and thus never replicates any of the other
+	parent thread into the child process. Most liburcu implementations
+	require that all registrations (as reader, defer_rcu and call_rcu
+	threads) should be released before a fork() is performed, except for the
+	rather common scenario where fork() is immediately followed by exec() in
+	the child process. The only implementation not subject to that rule is
+	liburcu-bp, which is designed to handle fork() by calling
+	rcu_bp_before_fork, rcu_bp_after_fork_parent and
+	rcu_bp_after_fork_child.
+
+	Applications that use call_rcu() are required to invoke
+	call_rcu_after_fork_child() from the child process after a
+	successful fork() system call that is not followed by exec().