futex.2: Minor wording fixes

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2015-07-28 10:04:10 +02:00
parent d45f244c6d
commit 9d32a39b82
1 changed files with 5 additions and 4 deletions

View File

@ -73,14 +73,15 @@ but these addresses all refer to the same location in physical memory.)
When executing a futex operation that requests to block a thread,
the kernel will block only if the futex word has the value that the
calling thread supplied as expected value.
The load from the futex word, the comparison with
the expected value,
calling thread supplied as the expected value of the futex word.
The loading of the futex word's value,
the comparison of that value with the expected value,
and the actual blocking will happen atomically and totally
ordered with respect to concurrently executing futex
operations on the same futex word.
Thus, the futex word is used to connect the synchronization in user space
with the implementation of blocking by the kernel; similar to an atomic
with the implementation of blocking by the kernel.
Like an atomic
compare-and-exchange operation that potentially changes shared memory,
blocking via a futex is an atomic compare-and-block operation.
.\" FIXME(Torvald Riegel):