Lines Matching full:store

42 	from or store to only part of the variable.
45 	use READ_ONCE() and WRITE_ONCE() or stronger to prevent load/store
46 	tearing, load/store fusing, and invented loads and stores.
195 load buffering, release-acquire chains, store buffering.
206 outcome in which the first load sees the value written by the second store
207 but the second load does not see the value written by the first store.
233 store, while the smp_load_acquire macro orders the load against any
276 (address dependency, as shown above), the value written by a later store
277 (data dependency), or whether or not a later store is executed in the
336 	 *	STORE $data			LOAD $data
338 	 *	STORE ->data_head		STORE ->data_tail
353 The LB pattern has one CPU load from one variable and then store to a
356 each load reads the value written by the other CPU's store.  In the
391 	 *	STORE $data			LOAD $data
393 	 *	STORE ->data_head		STORE ->data_tail
399 and the store to data combined with the user's full memory barrier
400 between the load from data and the store to ->data_tail prevents
438 It is tempting to assume that CPU0()'s store to x is globally ordered
439 before CPU1()'s store to z, but this is not the case:
471 Store buffering
474 Store buffering can be thought of as upside-down load buffering, so
514 On CPU0, the store is to @cond and the load is in waitqueue_active().
515 On CPU1, prepare_to_wait() contains both a store to wq_head and a call