Lines Matching +full:cpu +full:- +full:read
1 This document contains brief definitions of LKMM-related terms. Like most
2 glossaries, it is not intended to be read front to back (except perhaps
10 Address dependencies are quite common in RCU read-side critical
15 3 do_something(p->a);
18 In this case, because the address of "p->a" on line 3 is computed
21 "p->a". In rare cases, optimizing compilers can destroy address
28 using spin_lock(). With respect to a non-lock shared variable,
30 load before later memory references running on that same CPU.
40 See also "Happens-Before", "Reads-From", "Relaxed", and "Release".
42 Coherence (co): When one CPU's store to a given variable overwrites
43 either the value from another CPU's store or some later value,
44 there is said to be a coherence link from the second CPU to
47 It is also possible to have a coherence link within a CPU, which
52 See also "From-reads" and "Reads-from".
65 Please see control-dependencies.txt for more information.
69 Cycle: Memory-barrier pairing is restricted to a pair of CPUs, as the
73 In a cycle, each CPU's ordering interacts with that of the next:
75 CPU 0 CPU 1 CPU 2
80 CPU 0's smp_mb() interacts with that of CPU 1, which interacts
81 with that of CPU 2, which in turn interacts with that of CPU 0
105 From-Reads (fr): When one CPU's store to a given variable happened
106 too late to affect the value returned by another CPU's
107 load from that same variable, there is said to be a from-reads
110 It is also possible to have a from-reads link within a CPU, which
111 is a "from-reads internal" (fri) link. The term "from-reads
115 See also "Coherence" and "Reads-from".
118 its CPU's prior accesses with all of that CPU's subsequent
120 that orders all of its CPU's prior accesses, itself, and
121 all of its CPU's subsequent accesses.
123 Happens-Before (hb): A relation between two accesses in which LKMM
125 detail, please see the "THE HAPPENS-BEFORE RELATION: hb"
133 Pairing: "Memory-barrier pairing" reflects the fact that synchronizing
136 one of the CPUs and the other by the other CPU. Of course,
143 Reads-From (rf): When one CPU's load returns the value stored by some other
144 CPU, there is said to be a reads-from link from the second
145 CPU's store to the first CPU's load. Reads-from links have the
147 which means that algorithms using reads-from links can use lighter
149 coherence and from-reads links.
151 It is also possible to have a reads-from link within a CPU, which
152 is a "reads-from internal" (rfi) link. The term "reads-from
156 See also Coherence" and "From-reads".
159 READ_ONCE(), WRITE_ONCE(), a non-value-returning read-modify-write
160 operation, or a value-returning read-modify-write operation whose
166 using spin_unlock(). With respect to a non-lock shared variable,
168 store after earlier memory references that ran on that same CPU.
175 Unmarked Access: An access to a variable that uses normal C-language