torvalds/linux
torvalds/linux
2
0
Fork 0
mirror of git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git synced 2025-09-04 20:19:47 +08:00
Code

tools/memory-model/Documentation: Fix SRCU section in explanation.txt

Browse Source 
The SRCU read-side critical sections describes the difference between
srcu_down_read()/srcu_up_read() and srcu_read_lock()/srcu_read_unlock()
in a way that a last pair must occur on the same CPU.

This is not true, the srcu_read_unlock() can happen on any CPU, but it
must be performed by the same task that invoked srcu_read_lock().

Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
This commit is contained in:
Uladzislau Rezki (Sony) 2025-04-22 19:38:30 +02:00 committed by Paul E. McKenney
parent 730c0a8ee4
commit 5c9e006298
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
tools/memory-model/Documentation/explanation.txt
View File

@ -1896,7 +1896,7 @@ following respects:
3. The srcu_down_read() and srcu_up_read() primitives work 3. The srcu_down_read() and srcu_up_read() primitives work
exactly like srcu_read_lock() and srcu_read_unlock(), except exactly like srcu_read_lock() and srcu_read_unlock(), except
that matching calls don't have to execute on the same CPU. that matching calls don't have to execute within the same context.
(The names are meant to be suggestive of operations on (The names are meant to be suggestive of operations on
semaphores.) Since the matching is determined by the domain semaphores.) Since the matching is determined by the domain
pointer and index value, these primitives make it possible for pointer and index value, these primitives make it possible for