question on kernel rwsem behaviour
Hi all,
I just had a quick question on read-write semaphore semantics. Suppose someone holds a sema for reading, then someone else tries to aquire it for writing, and blocks. Finally, a third code path tries to aquire it for reading.
Does this third code path get the sema, or does it wait for the writer?
Based on looking at the implementation it seems like it waits, but I'd like to confirm that.
Thanks,
Chris
Quoted 8 lines · On Fri, 21 Sep 2007 09:38:44 -0600 "Chris Friesen" <[email protected]> wrote:
Hi all,
I just had a quick question on read-write semaphore semantics. Suppose someone holds a sema for reading, then someone else tries to aquire it for writing, and blocks. Finally, a third code path tries to aquire it for reading.
Quoted 4 lines
Does this third code path get the sema, or does it wait for the writer?
Based on looking at the implementation it seems like it waits, but I'd like to confirm that.
Yes, its fair in that sense.