summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorkeramida <keramida@FreeBSD.org>2005-01-06 16:16:17 +0000
committerkeramida <keramida@FreeBSD.org>2005-01-06 16:16:17 +0000
commite1b5b1978824e56634c4482379da9b9d7c8f727a (patch)
treeb5b152bc2818569d923ea4b57209880eb427adb4
parent6a05820e8bc561bb9a8de3a5d3722a10fd20f8ee (diff)
downloadFreeBSD-src-e1b5b1978824e56634c4482379da9b9d7c8f727a.zip
FreeBSD-src-e1b5b1978824e56634c4482379da9b9d7c8f727a.tar.gz
"non-spin" is better with a dash, than without.
-rw-r--r--share/man/man9/mutex.92
1 files changed, 1 insertions, 1 deletions
diff --git a/share/man/man9/mutex.9 b/share/man/man9/mutex.9
index 1fef49b..e4ca86f 100644
--- a/share/man/man9/mutex.9
+++ b/share/man/man9/mutex.9
@@ -126,7 +126,7 @@ These should only be used to protect data shared with any devices that
require non-preemptive interrupts, and low level scheduling code.
In most/all architectures both acquiring and releasing of a
uncontested spin mutex is more expensive than the same operation
-on a non spin mutex.
+on a non-spin mutex.
In order to protect an interrupt service routine from blocking
against itself all interrupts are blocked on a processor while
holding a spin lock.
OpenPOWER on IntegriCloud