Lines Matching refs:update

63 Splitting the update into removal and reclamation phases permits the
72 So the typical RCU update sequence goes something like the following:
90 This is because lock-based updaters typically update data items in place,
104 thread performs both the update step (step (a) above) and the reclamation
196 	it is illegal to block or where update-side performance is
202 	of automatically limiting update rate should grace periods
205 	update rate in order to gain this same sort of resilience.  See
206 	checklist.txt for some approaches to limiting the update rate.
425 o	Use rcu_assign_pointer() to update an RCU-protected pointer.
772 to rcu_read_lock() and rcu_read_unlock, update-side locking moves from
776 However, there is one potential catch: the read-side and update-side
780 a single atomic update, converting to RCU will require special care.
814 RCU pointer/list update:
915 e.	Is your workload too update-intensive for normal use of