Lines Matching refs:CPU

20 Local atomic operations are meant to provide fast and highly reentrant per CPU
25 Having fast per CPU atomic counters is interesting in many cases : it does not
31 CPU which owns the data. Therefore, care must taken to make sure that only one
32 CPU writes to the local_t data. This is done by using per cpu data and making
34 permitted to read local_t data from any CPU : it will then appear to be written
35 out of order wrt other memory writes by the owner CPU.
56 - _Only_ the CPU owner of these variables must write to them.
57 - This CPU can use local ops from any context (process, irq, softirq, nmi, ...)
61   different CPU between getting the per-cpu variable and doing the
64   taken on a mainline kernel, since they will run on the local CPU with
70 - Reads of these variables can be done from any CPU, because updates to
72   synchronization is done by the writer CPU, an outdated copy of the
106 relatively to other memory writes happening on the CPU that owns the data.
137 /* IPI called on each CPU. */
159 	printk("Counters read from CPU %d\n", smp_processor_id());
161 		printk("Read : CPU %d, count %ld\n", cpu,