From: "Chris Friesen" <cfriesen@nortel.com>
To: linux-kernel@vger.kernel.org
Subject: question on kernel rwsem behaviour
Date: Fri, 21 Sep 2007 09:38:44 -0600 [thread overview]
Message-ID: <46F3E584.4020301@nortel.com> (raw)
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
next reply other threads:[~2007-09-21 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 15:38 Chris Friesen [this message]
2007-09-21 20:11 ` question on kernel rwsem behaviour Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46F3E584.4020301@nortel.com \
--to=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox