Re: [patch 08/23] dynticks: prepare the RCU code
From: Ingo Molnar
Date: Sat Sep 30 2006 - 17:44:29 EST
* Dipankar Sarma <dipankar@xxxxxxxxxx> wrote:
> > secondly, i think i saw functionality problems when RCU was not
> > completed before going idle - for example synchronize_rcu() on
> > another CPU would hang.
> That is probably because of what I mention above. In the original
> CONFIG_NO_IDLE_HZ, we don't go into a nohz state if there are RCUs
> pending in that cpu.
hm. I just tried it and it seems completing RCU processing isnt even
necessary. I'll drop the RCU hackery. If we need anything then in
synchronize_rcu [which is a rare and slowpath op]: there (on NO_HZ) we
should tickle all cpus via an smp_call_function().
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/