aboutsummaryrefslogtreecommitdiffstats
path: root/man7/futex.7
diff options
context:
space:
mode:
Diffstat (limited to 'man7/futex.7')
-rw-r--r--man7/futex.712
1 files changed, 8 insertions, 4 deletions
diff --git a/man7/futex.7 b/man7/futex.7
index a958b25013..55371e934f 100644
--- a/man7/futex.7
+++ b/man7/futex.7
@@ -49,7 +49,8 @@ in which case the application is commonly called multithreaded.
.PP
Any futex operation starts in userspace,
but it may necessary to communicate with the kernel using the
-\fBfutex\fR(2) system call.
+.BR futex (2)
+system call.
.PP
To 'up' a futex, execute the proper assembler instructions that
will cause the host CPU to atomically increment the integer.
@@ -76,7 +77,9 @@ system call can optionally be passed a timeout specifying how long
the kernel should
wait for the futex to be upped.
In this case, semantics are more complex and the programmer is referred
-to \fBfutex\fR(2) for
+to
+.BR futex (2)
+for
more details.
The same holds for asynchronous futex waiting.
.SH "NOTES"
@@ -87,7 +90,8 @@ Implementors are expected to be assembly literate and to have read
the sources of the futex userspace library referenced
below.
.PP
-This man page illustrates the most common use of the \fBfutex\fR(2)
+This man page illustrates the most common use of the
+.BR futex (2)
primitives: it is by no means the only one.
.SH "AUTHORS"
.PP
@@ -103,7 +107,7 @@ but with different semantics from those described above.
Current semantics are available from Linux 2.5.40 onwards.
.SH "SEE ALSO"
.PP
-\fBfutex\fR(2),
+.BR futex (2),
`Fuss, Futexes and Furwocks: Fast Userlevel Locking in Linux'
(proceedings of the Ottawa Linux Symposium 2002),
futex example library, futex-*.tar.bz2