Searched refs:updater (Results 1 – 10 of 10) sorted by relevance
/linux-4.4.14/Documentation/dmaengine/ |
D | pxa_dma.txt | 46 | desc-sg[0] | ... | desc-sg[last] | status updater | finisher/linker | 53 - status updater 91 d) Transfers completion updater 94 descriptor of a transfer, the "status updater", will write the latest 107 - reading the physical channel last updater mark 112 updater mark.
|
/linux-4.4.14/drivers/dma/ |
D | pxa_dma.c | 578 struct pxad_desc_hw *updater = in set_updater_desc() local 582 updater->ddadr = DDADR_STOP; in set_updater_desc() 583 updater->dsadr = dma; in set_updater_desc() 584 updater->dtadr = dma + 8; in set_updater_desc() 585 updater->dcmd = PXA_DCMD_WIDTH4 | PXA_DCMD_BURST32 | in set_updater_desc() 588 updater->dcmd |= PXA_DCMD_ENDIRQEN; in set_updater_desc() 596 struct pxad_desc_hw *updater = in is_desc_completed() local 599 return updater->dtadr != (updater->dsadr + 8); in is_desc_completed()
|
/linux-4.4.14/Documentation/RCU/ |
D | rcu_dereference.txt | 219 void updater(void) 254 but you should not be. After all, the updater might have been invoked 272 void updater(void) 335 void updater(void)
|
D | whatisRCU.txt | 64 updater to perform the removal phase immediately, and to defer the 89 prevent an updater from deleting the data structure out from under them. 100 In the three-step procedure shown above, the updater is performing both 159 Marks the end of updater code and the beginning of reclaimer 216 The updater uses this function to assign a new value to an 218 in value from the updater to the reader. This function returns 291 reader, updater, and reclaimer. 304 | updater |<---------------------+ | 428 This primitive protects concurrent readers from the updater, 516 RCU distinction between updater, namely foo_update_a(), and reclaimer,
|
D | checklist.txt | 201 7. If the updater uses call_rcu() or synchronize_rcu(), then the 203 rcu_read_unlock(). If the updater uses call_rcu_bh() or 206 updater uses call_rcu_sched() or synchronize_sched(), then 209 If the updater uses synchronize_srcu() or call_srcu(), then
|
D | lockdep.txt | 84 from taking place. If the above statement was invoked only from updater
|
D | rcu.txt | 27 o How can the updater tell when a grace period has completed
|
D | RTFP.txt | 203 between memory barriers and read-side traversal order: If the updater 205 order, the updater need only execute a memory-barrier instruction, 206 but if in the same direction, the updater needs to wait for a grace 2641 If the updater is making changes in the opposite direction from 2642 the read-side traveral order, the updater need only execute a 2644 updater needs to wait for a grace period between the individual
|
D | rcubarrier.txt | 22 pre-existing readers have completed. An updater wishing to delete an
|
/linux-4.4.14/fs/afs/ |
D | callback.c | 369 server = container_of(work, struct afs_server, updater);
|