Lines Matching full:writer

4  * RT-specific reader/writer semaphores and reader/writer locks
26  *  2) Wake the writer waiting in down_write()/write_lock() #3
29  * locks on RT are not writer fair, but writers, which should be avoided in
33  * It's possible to make the rw primitives writer fair by keeping a list of
34  * active readers. A blocked writer would force all newly incoming readers
41  * The risk of writer starvation is there, but the pathological use cases
76 	 * Allow readers, as long as the writer has not completely  in __rwbase_read_lock()
89 	 * Reader1		Reader2		Writer  in __rwbase_read_lock()
97 	 *			wake(Writer)  in __rwbase_read_lock()
111 	 * That would put Reader1 behind the writer waiting on  in __rwbase_read_lock()
124 	 * On success the rtmutex is held, so there can't be a writer  in __rwbase_read_lock()
158 	 * Wake the writer, i.e. the rtmutex owner. It might release the  in __rwbase_read_unlock()
177 	 * rwb->readers can only hit 0 when a writer is waiting for the  in rwbase_read_unlock()