> In 2.5.44, stock from kernel.org, rcu_process_callbacks() calls
> local_irq_disable(). Is that just preemption disabling, now?
No, but rcu_process_callbacks() is for the copy update part.
Look at rcu_read_lock() and rcu_read_unlock()... those are the read
paths.
Of course, I can be very wrong about some of this, RCU grosses^Wconfuses
me. But the read paths do just seem to call rcu_read_lock/unlock which
just do a preempt_disable/enable. Otherwise the read path is entirely
transparent.
Robert Love
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/