diff options
author | 2013-04-18 14:25:03 -0700 | |
---|---|---|
committer | 2013-08-18 17:05:32 -0700 | |
commit | d84297c99bd9f63baf92c9f2d36582f879858664 (patch) | |
tree | 5fa42b0c2ef8ae93f016dd5b0ea318bc720f5482 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | rcu: Have the RCU tracepoints use the tracepoint_string infrastructure (diff) | |
download | linux-dev-d84297c99bd9f63baf92c9f2d36582f879858664.tar.xz linux-dev-d84297c99bd9f63baf92c9f2d36582f879858664.zip |
rcu: Fix rcu_barrier() documentation
There was a time when rcu_barrier() was guaranteed to wait for at least
a grace period, but that time ended due to energy-efficiency concerns.
So now rcu_barrier() is a no-op if there are no RCU callbacks queued in
the system. This commit updates the documentation to reflect this change.
Now, rcu_barrier() often does wait for a grace period, so, one could
imagine some modification to rcu_barrier() to more efficiently handle
cases where both rcu_barrier() and a grace period are needed. But this
must wait until someone shows a real-world need for a change.
Reported-by: Bob Copeland <bob@cozybit.com>
Reported-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Reviewed-by: Josh Triplett <josh@joshtriplett.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions