lkml.org 
[lkml]   [2006]   [Sep]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch 08/23] dynticks: prepare the RCU code

* Dipankar Sarma <dipankar@in.ibm.com> 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().

Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-09-30 23:47    [W:0.077 / U:0.256 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site