* question on kernel rwsem behaviour
@ 2007-09-21 15:38 Chris Friesen
2007-09-21 20:11 ` Peter Zijlstra
0 siblings, 1 reply; 2+ messages in thread
From: Chris Friesen @ 2007-09-21 15:38 UTC (permalink / raw)
To: linux-kernel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: question on kernel rwsem behaviour
2007-09-21 15:38 question on kernel rwsem behaviour Chris Friesen
@ 2007-09-21 20:11 ` Peter Zijlstra
0 siblings, 0 replies; 2+ messages in thread
From: Peter Zijlstra @ 2007-09-21 20:11 UTC (permalink / raw)
To: Chris Friesen; +Cc: linux-kernel
On Fri, 21 Sep 2007 09:38:44 -0600 "Chris Friesen"
<cfriesen@nortel.com> 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.
>
> 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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-09-21 20:13 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-09-21 15:38 question on kernel rwsem behaviour Chris Friesen
2007-09-21 20:11 ` Peter Zijlstra
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox