Lines Matching refs:SMP
57 - SMP barrier pairing.
395 address-dependency barriers; see the "SMP barrier pairing" subsection.
431 write barriers; see the "SMP barrier pairing" subsection.
452 see the "SMP barrier pairing" subsection.
543 the subsection on "SMP Barrier Pairing").
932 SMP BARRIER PAIRING
1833 TYPE MANDATORY SMP CONDITIONAL
1854 SMP memory barriers are reduced to compiler barriers on uniprocessor compiled
1859 [!] Note that SMP memory barriers _must_ be used to control the ordering of
1860 references to shared memory on SMP systems, though the use of locking instead
1863 Mandatory barriers should not be used to control SMP effects, since mandatory
1864 barriers impose unnecessary overhead on both SMP and UP systems. They may,
1866 windows. These barriers are required even on non-SMP systems as they affect
2305 On SMP systems locking primitives give a more substantial form of barrier: one
2345 work correctly, even if it's in an SMP kernel. There are, however, four
2437 The way to deal with this is to insert a general SMP memory barrier:
2917 Guests running within virtual machines might be affected by SMP effects even if
2918 the guest itself is compiled without SMP support. This is an artifact of
2919 interfacing with an SMP host while running an UP kernel. Using mandatory
2923 These have the same effect as smp_mb() etc when SMP is enabled, but generate
2924 identical code for SMP and non-SMP systems. For example, virtual machine guests
2926 (possibly SMP) host.