[ltt-dev] [rp] [PATCH urcu 4/4] Provide cleanup interfaces for per-CPU and per-thread call_rcu threads

[Paolo Bonzini]

On 03/09/2011 05:54 PM, Mathieu Desnoyers wrote:
> I'm just concerned about the execution order of the atfork callbacks. If
> we provide the callbacks directly, then the application can take care to
> call the various callbacks in a known order (e.g. first execute the
> call_rcu functions, and then the RCU lib functions).
> 
> If we use atfork, the order will be pretty much random, and I'm not sure
> I like that.

>From the man page:

       The  order  of calls to pthread_atfork() is significant. The parent and
       child fork handlers shall be called in the order  in  which  they  were
       established  by  calls  to pthread_atfork().  The prepare fork handlers
       shall be called in the opposite order.

It looks like call_rcu's atfork should be done first.

Paolo