diff options
| author | Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2013-12-05 14:56:54 -0800 |
|---|---|---|
| committer | Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2014-02-17 14:55:58 -0800 |
| commit | 6e67669678d2d51b2bcf0411aeb629b4353a9880 (patch) | |
| tree | 954ea91326c4ca225a698ccb3d6e3c3f8ee4b3d0 /Documentation/memory-barriers.txt | |
| parent | 6d0abeca3242a88cab8232e4acd7e2bf088f3bc2 (diff) | |
| download | talos-op-linux-6e67669678d2d51b2bcf0411aeb629b4353a9880.tar.gz talos-op-linux-6e67669678d2d51b2bcf0411aeb629b4353a9880.zip | |
documentation: Document call_rcu() safety mechanisms and limitations
The call_rcu() family of primitives will take action to accelerate
grace periods when the number of callbacks pending on a given CPU
becomes excessive. Although this safety mechanism can be useful,
it is no substitute for users of call_rcu() having rate-limit controls
in place. This commit adds this nuance to the documentation.
Reported-by: "Michael S. Tsirkin" <mst@redhat.com>
Reported-by: Gleb Natapov <gleb@redhat.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Reviewed-by: Josh Triplett <josh@joshtriplett.org>
Diffstat (limited to 'Documentation/memory-barriers.txt')
0 files changed, 0 insertions, 0 deletions
