Lines Matching +full:two +full:- +full:user

6 The basic idea behind RCU (read-copy update) is to split destructive
7 operations into two parts, one that prevents anyone from seeing the data
9 A "grace period" must elapse between the two parts, and this grace period
11 since dropped their references.  For example, an RCU-protected deletion
18 --------------------------
20 - Why would anyone want to use RCU?
22   The advantage of RCU's two-part approach is that RCU readers need
27   in read-mostly situations.  The fact that RCU readers need not
28   acquire locks can also greatly simplify deadlock-avoidance code.
30 - How can the updater tell when a grace period has completed
34   block, switch to user-mode execution, or enter the idle loop.
37   read-side critical sections.  So, if we remove an item from a
39   executed in user mode, or executed in the idle loop, we can
43   same effect, but require that the readers manipulate CPU-local
45   RCU read-side critical sections.  SRCU also uses CPU-local
46   counters, and permits general blocking within RCU read-side
50 - If I am running on a uniprocessor kernel, which can only do one
55 - How can I see where RCU is currently used in the Linux kernel?
65 - What guidelines should I follow when writing code that uses RCU?
69 - Why the name "RCU"?
71   "RCU" stands for "read-copy update".
73   this name came from, search for "read-copy update" to find it.
75 - I hear that RCU is patented?  What is with that?
81   There are now also LGPL implementations of user-level RCU
84 - I hear that RCU needs work in order to support realtime kernels?
86   Realtime-friendly RCU can be enabled via the CONFIG_PREEMPT_RCU
89 - Where can I find more information on RCU?