From 09ca31be6fab071aef6fc9d80b2f01d608aad61b Mon Sep 17 00:00:00 2001 From: khizmax Date: Thu, 22 Jan 2015 14:18:17 +0300 Subject: [PATCH] Corrected URCU doc --- cds/urcu/details/base.h | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/cds/urcu/details/base.h b/cds/urcu/details/base.h index b008581d..8aa28107 100644 --- a/cds/urcu/details/base.h +++ b/cds/urcu/details/base.h @@ -24,19 +24,17 @@ namespace cds { - [2011] M.Desnoyers, P.McKenney, A.Stern, M.Dagenias, J.Walpole "User-Level Implementations of Read-Copy Update" - Informal intruduction to user-space %RCU + Informal introduction to user-space %RCU [From Desnoyer's papers] %RCU is a synchronization mechanism that was added to the Linux kernel in October of 2002. %RCU achieves scalability improvements by allowing reads to occur concurrently with updates. In contrast to conventional locking primitives that ensure mutual exclusion among concurrent threads regardless of whether they be readers or updaters, or with reader-writer locks that allow concurrent reads - but not in the presence of updates, %RCU supports concurrency between a single updater - and multiple readers. %RCU ensures that reads are coherent by maintaining multiple - versions of objects and ensuring that they are not freed up until all pre-existing readside + but not in the presence of updates, %RCU supports concurrency between multiple updaters + and multiple readers. %RCU ensures that data are not freed up until all pre-existing critical sections complete. %RCU defines and uses efficient and scalable mechanisms - for publishing and reading new versions of an object, and also for deferring reclamation - of old versions. These mechanisms distribute the work among read and update + for deferring reclamation of old data. These mechanisms distribute the work among read and update paths in such a way as to make read paths extremely fast. %RCU readers execute within %RCU read-side critical sections. Each such critical section begins with -- 2.34.1