Searched refs:updater (Results 1 – 8 of 8) sorted by relevance
6 * This litmus test demonstrates that after a grace period, an RCU updater always
518 struct pxad_desc_hw *updater = in set_updater_desc() local522 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() local539 return updater->dtadr != (updater->dsadr + 8); in is_desc_completed()
235 void updater(void)274 but you should not be. After all, the updater might have been invoked292 void updater(void)362 void updater(void)
238 If the updater uses call_rcu() or synchronize_rcu(), then244 rcu_read_unlock_sched(). If the updater uses synchronize_srcu()252 a. If the updater uses synchronize_rcu_tasks() or257 b. If the updater uses call_rcu_tasks_trace()262 c. If an updater uses synchronize_rcu_tasks_rude(),
29 - How can the updater tell when a grace period has completed
265 value of the counter is ``s``, the updater must wait until the counter290 implemented by the ``exp_funnel_lock()`` function. The first updater295 number for the desired grace period or some later one, the updater
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 |
258 linked data structure without disrupting RCU readers. The updater uses390 #. At this point, only the updater has a reference to the newly removed799 | long would the updater be able to rely on there being no readers? |1282 without forcing the updater to wait for a grace period to elapse. The1367 | an updater using either call_rcu() or kfree_rcu() can proceed |1373 But what if the updater must wait for the completion of code to be