docs/rcu: update the api of call_rcu()
Subsystems (2)
PATCH 1/1 docs/rcu: update the api of call_rcu()
update the api of call_rcu()
Signed-off-by Hui Su <[email protected]>
--- Documentation/RCU/whatisRCU.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
Documentation/RCU/whatisRCU.rst +1 -2
@@ -497,8 +497,7 @@ long -- there might be other high-priority work to be done. In such cases, one uses call_rcu() rather than synchronize_rcu(). The call_rcu() API is as follows:: - void call_rcu(struct rcu_head * head, - void (*func)(struct rcu_head *head)); + void call_rcu(struct rcu_head *head, rcu_callback_t func); This function invokes func(head) after a grace period has elapsed. This invocation might happen from either softirq or process context,
Signature · 1 line
2.25.1
Paul E. McKenney
maintainerQuoted 3 lines · Hui Su
update the api of
call_rcu()Signed-off-by Hui Su <[email protected]>
Good point, the typedef is more compact. Queued, thank you!
Thanx, Paul
Quoted 22 lines
--- Documentation/RCU/whatisRCU.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)Documentation/RCU/whatisRCU.rst +1
-2@@ -497,8 +497,7 @@ long -- there might be other high-priority work to be done. In such cases, one uses call_rcu() rather than synchronize_rcu(). The call_rcu() API is as follows:: - void call_rcu(struct rcu_head * head, - void (*func)(struct rcu_head *head)); + void call_rcu(struct rcu_head *head, rcu_callback_t func); This function invokes func(head) after a grace period has elapsed. This invocation might happen from either softirq or process context,Signature · 1 line
2.25.1