Lines Matching full: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.
88 	be running while updates are in progress.  There are a number
107 	c.	Make updates appear atomic to readers.	For example,
108 		pointer updates to properly aligned fields will
119 	d.	Carefully order the updates and the reads so that readers
191 	e.	Updates must ensure that initialization of a given
222 	Restructure your code so that it batches the updates, allowing
287 	primitive will correspondingly delay updates.  In contrast,
298 		limit on this number, stalling updates as needed to allow
303 		One way to stall the updates is to acquire the update-side
306 		from ever ending.)  Another way to stall the updates
307 		is for the updates to use a wrapper function around
313 	b.	Limiting update rate.  For example, if updates occur only
317 		guarding updates with a global lock, limiting their rate.
319 	c.	Trusted update -- if updates can only be done manually by
326 		number of updates per grace period.
424 	a given subsystem delays only its own updates, not those of other
433 	over those updates sharing a given srcu_struct, rather than