2 .\" Copyright (C) 2001 Jason Evans <jasone@FreeBSD.org>. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice(s), this list of conditions and the following disclaimer as
9 .\" the first lines of this file unmodified other than the possible
10 .\" addition of one or more copyright notices.
11 .\" 2. Redistributions in binary form must reproduce the above copyright
12 .\" notice(s), this list of conditions and the following disclaimer in the
13 .\" documentation and/or other materials provided with the distribution.
15 .\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER(S) ``AS IS'' AND ANY
16 .\" EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
17 .\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
18 .\" DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER(S) BE LIABLE FOR ANY
19 .\" DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
20 .\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
21 .\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
22 .\" CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
23 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
24 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
53 .Nd kernel shared/exclusive lock
59 .Fn sx_init "struct sx *sx" "const char *description"
61 .Fn sx_init_flags "struct sx *sx" "const char *description" "int opts"
63 .Fn sx_destroy "struct sx *sx"
65 .Fn sx_slock "struct sx *sx"
67 .Fn sx_xlock "struct sx *sx"
69 .Fn sx_slock_sig "struct sx *sx"
71 .Fn sx_xlock_sig "struct sx *sx"
73 .Fn sx_try_slock "struct sx *sx"
75 .Fn sx_try_xlock "struct sx *sx"
77 .Fn sx_sunlock "struct sx *sx"
79 .Fn sx_xunlock "struct sx *sx"
81 .Fn sx_unlock "struct sx *sx"
83 .Fn sx_try_upgrade "struct sx *sx"
85 .Fn sx_downgrade "struct sx *sx"
87 .Fn sx_sleep "void *chan" "struct sx *sx" "int priority" "const char *wmesg" "int timo"
89 .Fn sx_xholder "struct sx *sx"
91 .Fn sx_xlocked "struct sx *sx"
93 .Cd "options INVARIANTS"
94 .Cd "options INVARIANT_SUPPORT"
96 .Fn sx_assert "struct sx *sx" "int what"
98 .Fn SX_SYSINIT "name" "struct sx *sx" "const char *description"
100 Shared/exclusive locks are used to protect data that are read far more often
101 than they are written.
102 Shared/exclusive locks do not implement priority propagation like mutexes and
103 reader/writer locks to prevent priority inversions, so
104 shared/exclusive locks should be used prudently.
106 Shared/exclusive locks are created with either
112 is a pointer to space for a
116 is a pointer to a null-terminated character string that describes the
117 shared/exclusive lock.
122 specifies a set of optional flags to alter the behavior of
124 It contains one or more of the following flags:
125 .Bl -tag -width SX_ADAPTIVESPIN
126 .It Dv SX_ADAPTIVESPIN
127 If the kernel is compiled with
128 .Cd "options ADAPTIVE_SX" ,
129 then lock operations for
131 will spin instead of sleeping while an exclusive lock holder is executing on
134 Witness should not log messages about duplicate locks being acquired.
140 Do not profile this lock.
142 Allow threads to recursively acquire exclusive locks for
145 Do not log any operations for this lock via
149 Shared/exclusive locks are destroyed with
153 must not be locked by any thread when it is destroyed.
155 Threads acquire and release a shared lock by calling
164 Threads acquire and release an exclusive lock by calling
173 A thread can attempt to upgrade a currently held shared lock to an exclusive
176 A thread that has an exclusive lock can downgrade it to a shared lock by
183 will return 0 if the shared/exclusive lock cannot be acquired immediately;
184 otherwise the shared/exclusive lock will be acquired and a non-zero value will
188 will return 0 if the shared lock cannot be upgraded to an exclusive lock
189 immediately; otherwise the exclusive lock will be acquired and a non-zero value
195 do the same as their normal versions but performing an interruptible sleep.
196 They return a non-zero value if the sleep has been interrupted by a signal
197 or an interrupt, otherwise 0.
199 A thread can atomically release a shared/exclusive lock while waiting for an
202 For more details on the parameters to this function,
207 .Cd "options INVARIANTS"
209 .Cd "options INVARIANT_SUPPORT" ,
214 for the assertions specified in
216 and panics if they are not met.
217 One of the following assertions must be specified:
218 .Bl -tag -width ".Dv SA_UNLOCKED"
220 Assert that the current thread has either a shared or an exclusive lock on the
222 lock pointed to by the first argument.
224 Assert that the current thread has a shared lock on the
229 Assert that the current thread has an exclusive lock on the
232 by the first argument.
234 Assert that the current thread has no lock on the
237 by the first argument.
240 In addition, one of the following optional assertions may be included with
247 .Bl -tag -width ".Dv SA_NOTRECURSED"
249 Assert that the current thread has a recursed lock on
251 .It Dv SA_NOTRECURSED
252 Assert that the current thread does not have a recursed lock on
257 will return a pointer to the thread which currently holds an exclusive lock on
259 If no thread holds an exclusive lock on
266 will return non-zero if the current thread holds the exclusive lock;
267 otherwise, it will return zero.
269 For ease of programming,
271 is provided as a macro frontend to the respective functions,
275 Algorithms that are aware of what state the lock is in should use either
276 of the two specific functions for a minor performance benefit.
280 macro is used to generate a call to the
282 routine at system startup in order to initialize a given
285 The parameters are the same as
287 but with an additional argument,
289 that is used in generating unique variable names for the related
290 structures associated with the lock and the sysinit routine.
292 A thread may not hold both a shared lock and an exclusive lock on the same
294 attempting to do so will result in deadlock.
296 A thread may hold a shared or exclusive lock on an
301 lock may not be acquired while holding a mutex.
302 Otherwise, if one thread slept while holding an
304 lock while another thread blocked on the same
306 lock after acquiring a mutex, then the second thread would effectively
307 end up sleeping while holding a mutex, which is not allowed.
316 Currently there is no way to assert that a lock is not held.
317 This is not possible in the
318 .No non- Ns Dv WITNESS
319 case for asserting that this thread
320 does not hold a shared lock.
322 .No non- Ns Dv WITNESS
327 assertions merely check that some thread holds a shared lock.
328 They do not ensure that the current thread holds a shared lock.