summaryrefslogtreecommitdiffstats
path: root/share/man/man9
diff options
context:
space:
mode:
authorattilio <attilio@FreeBSD.org>2013-08-09 11:24:29 +0000
committerattilio <attilio@FreeBSD.org>2013-08-09 11:24:29 +0000
commit3f74b0e634cf4f4b3796e44533e8318ef773c3e9 (patch)
tree04b25801739905ec5fe493144ba4312ddffb67b7 /share/man/man9
parent16c7563cf4ffce21e633bfb33a25ab16072fc75e (diff)
downloadFreeBSD-src-3f74b0e634cf4f4b3796e44533e8318ef773c3e9.zip
FreeBSD-src-3f74b0e634cf4f4b3796e44533e8318ef773c3e9.tar.gz
Give mutex(9) the ability to recurse on a per-instance basis.
Now the MTX_RECURSE flag can be passed to the mtx_*_flag() calls. This helps in cases we want to narrow down to specific calls the possibility to recurse for some locks. Sponsored by: EMC / Isilon storage division Reviewed by: jeff, alc Tested by: pho
Diffstat (limited to 'share/man/man9')
-rw-r--r--share/man/man9/mutex.912
1 files changed, 10 insertions, 2 deletions
diff --git a/share/man/man9/mutex.9 b/share/man/man9/mutex.9
index 628939f..782033c 100644
--- a/share/man/man9/mutex.9
+++ b/share/man/man9/mutex.9
@@ -225,8 +225,10 @@ or
lock, respectively, and also accept a
.Fa flags
argument.
-In both cases, the only flag presently available for lock acquires is
-.Dv MTX_QUIET .
+In both cases, the only flags presently available for lock acquires are
+.Dv MTX_QUIET
+and
+.Dv MTX_RECURSE .
If the
.Dv MTX_QUIET
bit is turned on in the
@@ -235,6 +237,12 @@ argument, then if
.Dv KTR_LOCK
tracing is being done,
it will be silenced during the lock acquire.
+If the
+.Dv MTX_RECURSE
+bit is turned on in the
+.Fa flags
+argument, then the mutex can be acquired recursively.
+.Pp
.Pp
The
.Fn mtx_trylock
OpenPOWER on IntegriCloud