cyclic xcall: use smp_no_rendevous_barrier as setup function parameter
In this case we call target function only on a single CPU and do not need any synchronization at the setup stage. It's a bit non-obvious but setup function of NULL means that smp_rendezvous_cpus waits for all CPUs to arrive at the rendezvous point, but without doing any actual setup. While using smp_no_rendevous_barrier means that each CPU proceeds on its own schedule without any synchronization whatsoever. MFC after: 3 weeks
This commit is contained in:
parent
1b88c87408
commit
34b3952bdd
@ -122,6 +122,6 @@ static void reprogram(cyb_arg_t arg, hrtime_t exp)
|
||||
static void xcall(cyb_arg_t arg, cpu_t *c, cyc_func_t func, void *param)
|
||||
{
|
||||
|
||||
smp_rendezvous_cpus((cpumask_t) (1 << c->cpuid), NULL,
|
||||
func, smp_no_rendevous_barrier, param);
|
||||
smp_rendezvous_cpus((cpumask_t) (1 << c->cpuid),
|
||||
smp_no_rendevous_barrier, func, smp_no_rendevous_barrier, param);
|
||||
}
|
||||
|
Loading…
Reference in New Issue
Block a user