From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Date: Sat, 7 Aug 2010 21:57:51 -0700

quoted text
> If I cover preemptible RCU's semantics, a first cut comes out like this:
> 
>  * In non-preemptible RCU implementations (TREE_RCU and TINY_RCU), it
>  * is illegal to block while in an RCU read-side critical section.  In
>  * preemptible RCU implementations (TREE_PREEMPT_RCU and TINY_PREEMPT_RCU)
>  * in CONFIG_PREEMPT kernel builds, RCU read-side critical sections may
>  * be preempted, but explicit blocking is illegal.  Finally, in preemptible
>  * RCU implementations in real-time (CONFIG_PREEMPT_RT) kernel builds,
>  * RCU read-side critical sections may be preempted and they may also
>  * block, but only when acquiring spinlocks that are subject to priority
>  * inheritance.
> 
> Does that seem reasonable?

Sounds good to me.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html