Lines Matching refs:be

7 to implement them for any given architecture and shows how they can be used
8 properly. It also stresses on the precautions that must be taken when reading
34 permitted to read local_t data from any CPU : it will then appear to be written
40 It can be done by slightly modifying the standard atomic operations : only
41 their UP variant must be kept. It typically means removing LOCK prefix (on
55 - Variables touched by local ops must be per cpu variables.
59 - Preemption (or interrupts) must be disabled when using local ops in
60   process context to   make sure the process won't be migrated to a
63 - When using local ops in interrupt context, no special care must be
70 - Reads of these variables can be done from any CPU, because updates to
73   variable can be read when reading some _other_ cpu's variables.
104 Those local counters can be read from foreign CPUs to sum the count. Note that
105 the data seen by local_read across CPUs must be considered to be out of order
113 between CPUs, explicit smp_wmb() and smp_rmb() memory barriers must be used
114 respectively on the writer and the reader CPUs. It would be the case if you use
116 be a smp_wmb() between the buffer write and the counter increment and also a