Searched refs:updater (Results 1 – 9 of 9) sorted by relevance
| /linux/drivers/dma/ |
| H A D | pxa_dma.c | 518 struct pxad_desc_hw *updater = in set_updater_desc() local 522 updater->ddadr = DDADR_STOP; in set_updater_desc() 523 updater->dsadr = dma; in set_updater_desc() 524 updater->dtadr = dma + 8; in set_updater_desc() 525 updater->dcmd = PXA_DCMD_WIDTH4 | PXA_DCMD_BURST32 | in set_updater_desc() 528 updater->dcmd |= PXA_DCMD_ENDIRQEN; in set_updater_desc() 536 struct pxad_desc_hw *updater = in is_desc_completed() local 539 return updater->dtadr != (updater->dsadr + 8); in is_desc_completed()
|
| /linux/Documentation/litmus-tests/rcu/ |
| H A D | RCU+sync+read.litmus | 6 * This litmus test demonstrates that after a grace period, an RCU updater always
|
| /linux/Documentation/RCU/ |
| H A D | whatisRCU.rst | 93 updater to perform the removal phase immediately, and to defer the 118 prevent an updater from deleting the data structure out from under them. 129 In the three-step procedure shown above, the updater is performing both 202 This temporal primitive marks the end of updater code and the 261 The updater uses this spatial macro to assign a new value to an 263 in value from the updater to the reader. This is a spatial (as 367 reader, updater, and reclaimer. 381 | updater |<----------------+ | 401 above shows the most common one. On the updater side, the rcu_assign_pointer(), 512 This primitive protects concurrent readers from the updater, [all …]
|
| H A D | rcu_dereference.rst | 235 void updater(void) 274 but you should not be. After all, the updater might have been invoked 292 void updater(void) 362 void updater(void)
|
| H A D | checklist.rst | 238 If the updater uses call_rcu() or synchronize_rcu(), then 244 rcu_read_unlock_sched(). If the updater uses synchronize_srcu() 252 a. If the updater uses synchronize_rcu_tasks() or 257 b. If the updater uses call_rcu_tasks_trace() 262 c. If an updater uses synchronize_rcu_tasks_rude(),
|
| H A D | rcu.rst | 29 - How can the updater tell when a grace period has completed
|
| /linux/Documentation/RCU/Design/Expedited-Grace-Periods/ |
| H A D | Expedited-Grace-Periods.rst | 265 value of the counter is ``s``, the updater must wait until the counter 290 implemented by the ``exp_funnel_lock()`` function. The first updater 295 number for the desired grace period or some later one, the updater
|
| /linux/Documentation/RCU/Design/Memory-Ordering/ |
| H A D | Tree-RCU-Memory-Ordering.rst | 119 | that new readers will see all of the updater's pre-grace-period | 120 | accesses and also guarantees that the updater's post-grace-period |
|
| /linux/Documentation/sound/kernel-api/ |
| H A D | writing-an-alsa-driver.rst | 2109 /* call updater, unlock before it */ 2166 /* call updater */
|