Hello,
On Tue, 30 Apr 2013, Simon Horman wrote:
> This is intended for use in loops which read data protected by RCU and may
> have a large number of iterations. Such an example is dumping the list of
> connections known to IPVS: ip_vs_conn_array() and ip_vs_conn_seq_next().
>
> The call to cond_resched() is guarded by #ifndef CONFIG_PREEMPT_RCU as in
> the case of CONFIG_PREEMPT_RCU _rcu_read_unlock() will check to see if the
> RCU core needs to be informed, so there is no need to invoke cond_resched()
> in that case. Thanks to Paul E. McKenney for explaining this.
>
> cond_resched_rcu_lock() suggested by Eric Dumazet.
> ifndef guard suggested by Paul E. McKenney and Julian Anastasov.
>
> Cc: Eric Dumazet <eric.duma...@gmail.com>
> Cc: Paul E. McKenney <paul...@linux.vnet.ibm.com>
> Cc: Julian Anastasov <j...@ssi.bg>
> Acked-by: Ingo Molnar <mi...@kernel.org>
> Signed-off-by: Simon Horman <ho...@verge.net.au>
>
> ---
>
> v2
> * Add guard the call to cond_resched()
> ---
> include/linux/sched.h | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/include/linux/sched.h b/include/linux/sched.h
> index e692a02..66da71c 100644
> --- a/include/linux/sched.h
> +++ b/include/linux/sched.h
> @@ -2787,3 +2787,14 @@ static inline unsigned long rlimit_max(unsigned int
> limit)
> }
>
> #endif
> +
> +static void inline cond_resched_rcu_lock(void)
> +{
> + if (need_resched()) {
Ops, it should be without above need_resched.
> + rcu_read_unlock();
> +#ifndef CONFIG_PREEMPT_RCU
> + cond_resched();
> +#endif
> + rcu_read_lock();
> + }
> +}
> --
> 1.8.2.1
Regards
--
Julian Anastasov <j...@ssi.bg>
--
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/
