Lines Matching refs:update
26 1. Does the update code have proper mutual exclusion?
54 rcu_read_lock_sched(), or by the appropriate update-side lock.
58 3. Does the update code tolerate concurrent accesses?
65 a. Use the RCU variants of the list and hlist update
91 readers see valid data at all phases of the update.
131 perfectly legal (if redundant) for update-side code to
224 usually results in simpler code. So, unless update performance is
237 code using call_rcu() should explicitly limit update rate in
252 One way to stall the updates is to acquire the update-side
262 b. Limiting update rate. For example, if updates occur only
268 c. Trusted update -- if updates can only be done manually by
294 critical section or must be protected by appropriate update-side
302 primitives when the update-side lock is held is that doing so
308 and you don't hold the appropriate update-side lock, you -must-
414 RCU update-side primitives to deal with this.