Searched refs:updater (Results 1 – 14 of 14) sorted by relevance
| /Linux-v6.1/Documentation/driver-api/dmaengine/ |
| D | pxa_dma.rst | 51 | desc-sg[0] | ... | desc-sg[last] | status updater | finisher/linker |
60 - status updater
109 d) Transfers completion updater
112 descriptor of a transfer, the "status updater", will write the latest
127 - reading the physical channel last updater mark
134 updater mark.
|
| /Linux-v6.1/Documentation/litmus-tests/rcu/ |
| D | RCU+sync+read.litmus | 6 * This litmus test demonstrates that after a grace period, an RCU updater always
|
| /Linux-v6.1/drivers/dma/ |
| D | pxa_dma.c | 519 struct pxad_desc_hw *updater = in set_updater_desc() local
523 updater->ddadr = DDADR_STOP; in set_updater_desc()
524 updater->dsadr = dma; in set_updater_desc()
525 updater->dtadr = dma + 8; in set_updater_desc()
526 updater->dcmd = PXA_DCMD_WIDTH4 | PXA_DCMD_BURST32 | in set_updater_desc()
529 updater->dcmd |= PXA_DCMD_ENDIRQEN; in set_updater_desc()
537 struct pxad_desc_hw *updater = in is_desc_completed() local
540 return updater->dtadr != (updater->dsadr + 8); in is_desc_completed()
|
| /Linux-v6.1/Documentation/RCU/ |
| D | whatisRCU.rst | 85 updater to perform the removal phase immediately, and to defer the
110 prevent an updater from deleting the data structure out from under them.
121 In the three-step procedure shown above, the updater is performing both
182 Marks the end of updater code and the beginning of reclaimer
239 The updater uses this function to assign a new value to an
241 in value from the updater to the reader. This macro does not
335 reader, updater, and reclaimer.
349 | updater |<----------------+ |
366 above shows the most common one. On the updater side, the rcu_assign_pointer(),
475 This primitive protects concurrent readers from the updater,
[all …]
|
| D | rcu_dereference.rst | 221 void updater(void)
256 but you should not be. After all, the updater might have been invoked
274 void updater(void)
338 void updater(void)
|
| D | checklist.rst | 223 If the updater uses call_rcu() or synchronize_rcu(), then
229 rcu_read_unlock_sched(). If the updater uses synchronize_srcu()
235 If the updater uses call_rcu_tasks() or synchronize_rcu_tasks(),
237 context switches, that is, from blocking. If the updater uses
240 rcu_read_unlock_trace(). If an updater uses call_rcu_tasks_rude()
|
| D | rcu.rst | 29 - How can the updater tell when a grace period has completed
|
| D | lockdep.rst | 88 from taking place. If the above statement was invoked only from updater
|
| 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.rst | 25 pre-existing readers have completed. An updater wishing to delete an
|
| /Linux-v6.1/Documentation/RCU/Design/Expedited-Grace-Periods/ |
| 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-v6.1/Documentation/RCU/Design/Memory-Ordering/ |
| 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-v6.1/Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 258 linked data structure without disrupting RCU readers. The updater uses
390 #. At this point, only the updater has a reference to the newly removed
799 | 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. The
1367 | 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
|
| /Linux-v6.1/Documentation/sound/kernel-api/ |
| D | writing-an-alsa-driver.rst | 2203 /* call updater, unlock before it */
2256 /* call updater */
|
