Lines Matching full:pending

28  * Do we have a writer or someone pending. Note, some cases require checking
30  * nuance here. As a general rule of thumb, when locking, the pending writers
42  * Taking a namespace read lock requires that there is no writer (or pending) on
55  * 1) Any active or pending writer on the controller lock. They block and starve
57  * 2) Any active or pending writers on the namespace lock. We must wait in line.
58  * 3) Any active readers on the namespace lock. We ignore pending namespace
72  * there are outstanding or pending writers on the controller lock. We can
86  * 1) Any controller write lock or pending write
87  * 2) Any controller read lock. We skip pending reads because if they exist,
89  * 3) Any namespace having a write lock. We ignore pending writes because by
91  * 4) Any read lock on a namespace. We ignore pending reads like in the
114  * Answer can we hand off the world to a pending controller write lock. This has
115  * similar rules to the above; however, we critically _ignore_ pending
142  * Namespace handoff variant. It skips pending writers on the namespace lock,
264  * 2) Evaluate if there are pending readers for the controller. If so, wake up
269  * 1) Evaluate if there are pending writers and they can take the write lock. If
271  * 2) Otherwise, if there are pending readers. If so, wake up each and every
289 	 * If there are pending writers, either one of them will be woken up or  in nvme_rwlock_wakeup()
423 	 * For someone that was blocked, we need to remove them from the pending  in nvme_rwlock_signal()
457  * 3) A read lock can be taken if there are no pending or active writers on the