Lines Matching full:exclusive

52 .Nd kernel shared/exclusive lock
100 Shared/exclusive locks are used to protect data that are read far more often
102 Shared/exclusive locks do not implement priority propagation like mutexes and
104 shared/exclusive locks should be used prudently.
106 Shared/exclusive locks are created with either
117 shared/exclusive lock.
135 Allow threads to recursively acquire exclusive locks for
151 Shared/exclusive locks are destroyed with
166 Threads acquire and release an exclusive lock by calling
175 A thread can attempt to upgrade a currently held shared lock to an exclusive
178 A thread that has an exclusive lock can downgrade it to a shared lock by
185 will return 0 if the shared/exclusive lock cannot be acquired immediately;
186 otherwise the shared/exclusive lock will be acquired and a non-zero value will
190 will return 0 if the shared lock cannot be upgraded to an exclusive lock
191 immediately; otherwise the exclusive lock will be acquired and a non-zero value
201 A thread can atomically release a shared/exclusive lock while waiting for an
222 Assert that the current thread has either a shared or an exclusive lock on the
231 Assert that the current thread has an exclusive lock on the
259 will return a pointer to the thread which currently holds an exclusive lock on
261 If no thread holds an exclusive lock on
268 will return non-zero if the current thread holds the exclusive lock;
300 A thread may not hold both a shared lock and an exclusive lock on the same
304 A thread may hold a shared or exclusive lock on an
336 can only assert that the current thread does not hold an exclusive lock.