Lines Matching +full:store +full:- +full:release

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,
35 	When an acquire load returns the value stored by a release store
37 	from" the release store), then all operations preceding that
38 	store "happen before" any operations following that load acquire.
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,
52 	See also "From-reads" and "Reads-from".
54 Control Dependency:  When a later store's execution depends on a test
56 	a "control dependency" extends from that load to that store.
65 	Please see control-dependencies.txt for more information.
69 Cycle:	Memory-barrier pairing is restricted to a pair of CPUs, as the
88 Data Dependency:  When the data written by a later store is computed based
90 	extends from that load to that later store.  For example:
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
108 	link from the load to the store.
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
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
146 	nice property that time must advance from the store to the load,
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
163 	See also "Acquire" and "Release".
165 Release:  With respect to a lock, releasing that lock, for example,
166 	using spin_unlock().  With respect to a non-lock shared variable,
167 	a special operation that includes a store and which orders that
168 	store after earlier memory references that ran on that same CPU.
169 	An example special release store is smp_store_release(), but
171 	release stores.
175 Unmarked Access:  An access to a variable that uses normal C-language