Re: [PATCH RFC] v5 expedited "big hammer" RCU grace periods

[Evgeniy Polyakov]

Hi.

On Sun, May 17, 2009 at 12:11:41PM -0700, Paul E. McKenney (paulmck@xxxxxxxxxxxxxxxxxx) wrote:
> Fifth cut of "big hammer" expedited RCU grace periods.  This uses per-CPU
> kthreads that are scheduled in parallel by a call to smp_call_function()
> by yet another kthread.  The synchronize_sched(), synchronize_rcu(),
> and synchronize_bh() primitives wake this kthread up and then wait for
> it to force the grace period.

I'm curious, but doesn't the fact that registered 'barrier' callback is
invoked mean grace period completion? I.e. why to bother with
rescheduling, waiting for thread to complete and so on, when we only
care in the fact that 'barrier' callback is invoked, and thus all
previous ones are completed?
Or it is done just for the simplicity, since all rescheduling machinery
already manages the rcu bits correctly, so you do not want to put it
directly into 'barrier' callback?

-- 
	Evgeniy Polyakov
--
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/