![]() | |||||||||||||
Messages in this thread |
* Peter Zijlstra <peter@programming.kicks-ass.net> wrote: > > i think the 'migrate read-count' method is not adequate either, because > > all callbacks queued within an RCU read section must be called after the > > lock has been dropped - while with the migration method CPU#1 would be > > free to process callbacks queued in the RCU read section still active on > > CPU#2. > > how about keeping the rcu callback list in process context and only > splice it to a global (per cpu) list on rcu_read_unlock? hm, that would indeed solve this problem. It would also solve the grace period problem: all callbacks in the global (per-CPU) list are immediately processable. Paul? 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: 2005-04-06 13:30 [W:2.353 / U:0.020 seconds] ©2003-2008 Jasper Spaans | |||||||||||||