Lines Matching full:from
9 dependency" extends from that load extending to the later access.
19 from the value returned by the rcu_dereference() on line 2, the
20 address dependency extends from that rcu_dereference() to that
37 from" the release store), then all operations preceding that
40 See also "Happens-Before", "Reads-From", "Relaxed", and "Release".
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
52 See also "From-reads" and "Reads-from".
55 of a value computed from a value returned by an earlier load,
56 a "control dependency" extends from that load to that store.
62 Here, the control dependency extends from the READ_ONCE() on
90 extends from that load to that later store. For example:
95 In this case, the data dependency extends from the READ_ONCE()
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".
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".