Lines Matching refs:general

415      A general memory barrier gives a guarantee that all the LOAD and STORE
420      A general memory barrier is a partial ordering over both loads and stores.
834 including of course general barriers.  A write barrier pairs with a data
836 barrier, a read barrier, or a general barrier.  Similarly a read barrier,
838 barrier, an acquire barrier, a release barrier, or a general barrier:
863 	<general barrier>
1266 				<general barrier>	<general barrier>
1281 In the Linux kernel, use of general memory barriers guarantees
1287 For example, suppose that CPU 2's general barrier in the above example
1294 				<read barrier>		<general barrier>
1308 To reiterate, if your code requires transitivity, use general barriers
1334 This is a general barrier -- there are no read-read or write-write
1961 A general memory barrier is interpolated automatically by set_current_state()
1969 	    <general barrier>
1977 which therefore also imply a general memory barrier after setting the state.
2010 	    <general barrier>		  STORE current->state
2296 The way to deal with this is to insert a general SMP memory barrier:
2326 about the state (old or new) implies an SMP-conditional general memory barrier
2429      so for _all_ general drivers locks should be used and mmiowb() must be