Lines Matching full:blocking

30  * - blocking lock semantics
39  * is done by read-write spinlock and the blocking part is implemented using
45  * blocking semantics - the low-level rwlock is not held but the counter
46  *                      denotes how many times the blocking lock was held;
91  * Locking pattern - blocking
94  * The blocking write uses the following scheme.  The +--+ denotes the spinning
106  * Blocking read is similar.
188  * Mark already held read lock as blocking. Can be nested in write lock by the
194  * The rwlock is released and blocking reader counter is increased.
213  * Mark already held write lock as blocking.
218  * The rwlock is released and blocking writers is set.
239  * Lock the extent buffer for read. Wait for any writers (spinning or blocking).
291  * contending blocking writers. If there are, don't wait.
386  * Release read lock, previously set to blocking by a pairing call to
414  * Lock for write. Wait for all blocking and spinning readers and writers. This
450  * Release the write lock, either blocking or spinning (ie. there's no need
451  * for an explicit blocking unlock, like btrfs_tree_read_unlock_blocking).
489  * Set all locked nodes in the path to blocking locks.  This should be done
501 		 * will bump the count of blocking holders and drop the  in btrfs_set_path_blocking()