Re: [PATCH tip/core/rcu 6/7] rcu: Drive quiescent-state-forcingdelay from HZ

[Peter Zijlstra]

> In theory, yes.  In practice, this requires lots of lock acquisitions
> and releases on large systems, including some global locks.  The weight
> could be reduced, but...
> 
> What I would like to do instead would be to specify expedited grace
> periods during boot.

But why, surely going idle without any RCU callbacks isn't completely unheard
of, even outside of the boot process?

Being able to quickly drop out of the RCU state machinery would be a good thing IMO.

>  The challenge here appears to be somehow telling
> RCU when boot is done.  The APIs are there from an RCU viewpoint:  boot
> with rcupdate.rcu_expedited=1, then, once boot is complete (whatever
> that means on your platform) "echo 0 > /sys/kernel/rcu_expedited".

Ha, and here you assume userspace is sane and co-operative. Fail in my book ;-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/