Lines Matching refs:updates

28 	for lockless updates.  This does result in the mildly
30 	rcu_read_unlock() are used to protect updates, however, this
41 	c.	restricting updates to a single task.
78 	be running while updates are in progress.  There are a number
97 	c.	Make updates appear atomic to readers.	For example,
98 		pointer updates to properly aligned fields will
106 	d.	Carefully order the updates and the reads so that
208 	Restructure your code so that it batches the updates, allowing
250 	primitive will correspondingly delay updates.  In contrast,
261 		limit on this number, stalling updates as needed to allow
266 		One way to stall the updates is to acquire the update-side
269 		from ever ending.)  Another way to stall the updates
270 		is for the updates to use a wrapper function around
276 	b.	Limiting update rate.  For example, if updates occur only
280 		guarding updates with a global lock, limiting their rate.
282 	c.	Trusted update -- if updates can only be done manually by
293 		number of updates per grace period.
392 	a given subsystem delays only its own updates, not those of other
401 	over those updates sharing a given srcu_struct, rather than