X-Git-Url: https://git.liburcu.org/?p=urcu.git;a=blobdiff_plain;f=README;h=ec0d6a22b79c165a87cac300c6964e846f79c5a8;hp=10406f79f9b33b797e794ca463d97a5c7cf0378f;hb=47c5a84f6137e1cb2fcbf448a134a0485d6f102e;hpb=d123233afd72d7556d8eec3a1cf07b0af7b4b3d2

diff --git a/README b/README
index 10406f7..ec0d6a2 100644
--- a/README
+++ b/README
@@ -190,3 +190,15 @@ 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 this case.