Lines Matching +full:pairs +full:- +full:one

1 This document contains brief definitions of LKMM-related terms.  Like most
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,
40 	See also "Happens-Before", "Reads-From", "Relaxed", and "Release".
42 Coherence (co):  When one CPU's store to a given variable overwrites
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
105 From-Reads (fr):  When one CPU's store to a given variable happened
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".
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
135 	Memory barriers thus tend to come in pairs, one executed by
136 	one of the CPUs and the other by the other CPU.  Of course,
138 	smp_store_release() pairs with an smp_load_acquire() that reads
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,
175 Unmarked Access:  An access to a variable that uses normal C-language