X-Git-Url: http://git.lttng.org/?p=userspace-rcu.git;a=blobdiff_plain;f=README;h=f7f0dece2249bb764af9932a35cbf1ca57abffa3;hp=b6d2ae48d0b3365ccd0aa4344bc95f24ed6daef3;hb=4cf1675fa5feb3a2e9e9f965e516e55fbf411457;hpb=f9edede0c2229e5d92d0480d358eb2d14f2a8229

diff --git a/README b/README
index b6d2ae4..f7f0dec 100644
--- a/README
+++ b/README
@@ -201,6 +201,6 @@ Interaction with fork()
 	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 by requiring a call to
-	synchronize_rcu() following the fork() in the child before any new
-	thread is created.
+	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.