All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "Chris Friesen" <cfriesen@nortel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: question on kernel rwsem behaviour
Date: Fri, 21 Sep 2007 22:11:22 +0200	[thread overview]
Message-ID: <20070921221122.7776e0ec@lappy> (raw)
In-Reply-To: <46F3E584.4020301@nortel.com>

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.

      reply	other threads:[~2007-09-21 20:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-21 15:38 question on kernel rwsem behaviour Chris Friesen
2007-09-21 20:11 ` Peter Zijlstra [this message]

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=20070921221122.7776e0ec@lappy \
    --to=peterz@infradead.org \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.