aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/include/linux/sched.h
diff options
context:
space:
mode:
authorDavid Vernet <void@manifault.com>2022-03-29 15:26:13 -0700
committerPaul E. McKenney <paulmck@kernel.org>2022-04-20 16:51:11 -0700
commitf1efe84d6fd2af163989025bc285ff9b3b0c764f (patch)
tree6e882fa8778f703f3c037285441f3158e479b9b6 /include/linux/sched.h
parentrcu: Check for successful spawn of ->boost_kthread_task (diff)
downloadwireguard-linux-f1efe84d6fd2af163989025bc285ff9b3b0c764f.tar.xz
wireguard-linux-f1efe84d6fd2af163989025bc285ff9b3b0c764f.zip
rcu_sync: Fix comment to properly reflect rcu_sync_exit() behavior
The rcu_sync_enter() function is used by updaters to force RCU readers (e.g. percpu-rwsem) to use their slow paths during an update. This is accomplished by setting the ->gp_state of the rcu_sync structure to GP_ENTER. In the case of percpu-rwsem, the readers' slow path waits on a semaphore instead of just incrementing a reader count. Each updater invokes the rcu_sync_exit() function to signal to readers that they may again take their fastpaths. The rcu_sync_exit() function sets the ->gp_state of the rcu_sync structure to GP_EXIT, and if all goes well, after a grace period the ->gp_state reverts back to GP_IDLE. Unfortunately, the rcu_sync_enter() function currently has a comment incorrectly stating that rcu_sync_exit() (by an updater) will re-enable reader "slowpaths". This patch changes the comment to state that this function re-enables reader fastpaths. Signed-off-by: David Vernet <void@manifault.com> Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Diffstat (limited to 'include/linux/sched.h')
0 files changed, 0 insertions, 0 deletions