That's what I thought, thanks for confirming my understanding.
I still miss something about URCU's implementation.
How would a code that operates on multiple structures look like,
as all the api functions are context free (read_lock(), rcu_synchronize(),
etc. have no parameters)?
Thanks,
Ilya
On
> Studying the API of URCU it seems that it's mostly intended for
> link-based data structures, such a lists. Suppose I have a large
> struct that is often accessed by many readers, and some writers that
> occasionally update few fields each time. If I understand correctly,
> using URCU, the writer
Hi,
Studying the API of URCU it seems that it's mostly intended for link-based
data structures, such a lists. Suppose I have a large struct that is often
accessed by many readers, and some writers that occasionally update few
fields each time. If I understand correctly, using URCU, the writers wou
