Lines Matching refs:updates

32 	for lockless updates.  This does result in the mildly
34 	rcu_read_unlock() are used to protect updates, however, this
45 	c.	restricting updates to a single task.
82 	be running while updates are in progress.  There are a number
101 	c.	Make updates appear atomic to readers.	For example,
102 		pointer updates to properly aligned fields will
110 	d.	Carefully order the updates and the reads so that
209 	Restructure your code so that it batches the updates, allowing
251 	primitive will correspondingly delay updates.  In contrast,
262 		limit on this number, stalling updates as needed to allow
267 		One way to stall the updates is to acquire the update-side
270 		from ever ending.)  Another way to stall the updates
271 		is for the updates to use a wrapper function around
277 	b.	Limiting update rate.  For example, if updates occur only
281 		guarding updates with a global lock, limiting their rate.
283 	c.	Trusted update -- if updates can only be done manually by
290 		number of updates per grace period.
368 	a given subsystem delays only its own updates, not those of other
377 	over those updates sharing a given srcu_struct, rather than