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.
87 be running while updates are in progress. There are a number
106 c. Make updates appear atomic to readers. For example,
107 pointer updates to properly aligned fields will
115 d. Carefully order the updates and the reads so that
185 e. Updates must ensure that initialization of a given
214 Restructure your code so that it batches the updates, allowing
269 primitive will correspondingly delay updates. In contrast,
280 limit on this number, stalling updates as needed to allow
285 One way to stall the updates is to acquire the update-side
288 from ever ending.) Another way to stall the updates
289 is for the updates to use a wrapper function around
295 b. Limiting update rate. For example, if updates occur only
299 guarding updates with a global lock, limiting their rate.
301 c. Trusted update -- if updates can only be done manually by
308 number of updates per grace period. Better yet, periodically
394 a given subsystem delays only its own updates, not those of other
403 over those updates sharing a given srcu_struct, rather than