Lines Matching refs:fences

298 	fences), such as calls to smp_rmb() or rcu_read_lock().
737 only internal operations.  However, loads, stores, and fences involve
777 about the fence.  However, fences do constrain the way CPUs and the
784 	Strong fences, including smp_mb() and synchronize_rcu(), force
794 	Acquire fences, such as smp_load_acquire(), force the CPU to
799 	Release fences, such as smp_store_release(), force the CPU to
820 The propagation ordering enforced by release fences and strong fences
823 fence.  We describe this property by saying that release fences and
824 strong fences are A-cumulative.  By contrast, smp_wmb() fences are not
829 rcu_read_lock(), rcu_read_unlock(), and synchronize_rcu() fences have
836 The fences which affect propagation order (i.e., strong, release, and
837 smp_wmb() fences) are collectively referred to as cumul-fences, even
1170 The LKMM requires that smp_rmb(), acquire fences, and strong fences
1274 Less trivial examples of prop all involve fences.  Unlike the simple
1326 followed by two fences and an rfe link, utilizing the fact that
1327 release fences are A-cumulative:
1370 particular properties of strong fences, which we cover in the next
1378 features of strong fences.  It links two events E and F whenever some
1381 F via a coe or fre link, an arbitrary number of cumul-fences, an
1414 fences:
1446 before itself.  Thus, adding smp_mb() fences to the SB pattern
1513 to propagate to every CPU are fulfilled by placing strong fences at
1781 because all the other parts (fences and rfe) are already included in
1787 accesses and fences, such as those corresponding to smp_load_acquire()
1789 and fences; rather, they are read events with an annotation marking
1816 There are a few oddball fences which need special treatment:
1819 annotations for them; they act as strong fences just like smp_mb()