Map symbols to allow multiple RCU flavors to be used in one binary

[urcu.git] / README

diff --git a/README b/README
index ec0d6a22b79c165a87cac300c6964e846f79c5a8..56e98d768e960ede0a80245a8a1a725218de33d4 100644 (file)
--- a/README
+++ b/README
@@ -201,4 +201,10 @@ 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
        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.
+       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().