Hi Adam, On 06/16/2012 03:19 AM, Adam Hraska wrote: > I just wanted to let you know that my RCU code is publicly > available at: > lp:~adam-hraska+lp/helenos/rcu > > The branch currently contains only a single commit. > > Plan for the next week (till Sunday 24.6.): have the basic > rcu api implemented even if not 100% stable. This includes > rcu_read_lock/unlock, rcu_synchronize, rcu_call, but not > others like rcu_synchronize_barrier or rcu_synchronize_exped.
Thanks for sharing your branch location with us. Note that by now, we are approximately in the quarter of the coding period and there are only three weeks left before the midterm evaluations start. Your progress should be reflecting this. My advice to get you back on track would therefore be to pick for example RCU classic (or some other simple RCU with non-blocking readers) and go with that for the purpose of your GSoC project. It is not that much important to pick the most scalable RCU algorithm right now as it is to implement a scalable hash table data structure with non-blocking readers and convert parts of the kernel to use it. Since the RCU interface does not change much or at all for different RCU implementations, it should be possible to replace the RCU implementation later with something different. Jakub _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/cgi-bin/listinfo/helenos-devel
