Messages in this thread | | | Date | Fri, 21 Sep 2007 22:11:22 +0200 | From | Peter Zijlstra <> | Subject | Re: question on kernel rwsem behaviour |
| |
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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |