On Sun, Apr 21, 2013 at 11:56:09AM -0700, Paul E. McKenney wrote:
> CONFIG_RCU_FAST_NO_HZ will definitely change the timing, for example,
> increasing grace-period durations by up to a factor of four.
>
> One way to figure out if this is the problem would be to either (1)
> apply the following patch (assuming you have no more than a few tens
> of CPUs)
Only 8 - I'm modest that way :)
> or (2) setting the sysfs rcutree.rcu_expedited variable to 1 just before
> suspending the system.
>
> Either approach will force RCU to always use the faster expedited
> grace periods for synchronize_rcu() and friends. They will -not- help
> if someone has open-coded synchronize_rcu() in terms of call_rcu(),
> though.
Right,
# echo 1 > /sys/kernel/rcu_expedited
helped.
No warning, no delay, 2 suspend/resume cycles back-to-back. So, a
probable fix could be to force-enable the expedited grace periods during
suspend...?
Hmmm.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
