From: Lee Revell <rlrevell@joe-job.com>
To: Christopher Friesen <cfriesen@nortel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: any fairness in NTPL pthread mutexes?
Date: Mon, 31 Oct 2005 13:06:05 -0500 [thread overview]
Message-ID: <1130781965.32101.63.camel@mindpipe> (raw)
In-Reply-To: <43665B08.6040005@nortel.com>
On Mon, 2005-10-31 at 11:57 -0600, Christopher Friesen wrote:
> I'm using NPTL.
>
> If I have a pthread mutex currently owned by a task, and two other tasks
> try to lock it, when the mutex is unlocked, are there any rules about
> the order in which the waiting tasks get the mutex (ie priority, FIFO,
> etc.)?
I believe it's currently FIFO in violation of POSIX which specifies
priority based wakeup. AIUI one of the main goals of the realtime &
robust mutexes work is to fix this.
Lee
next prev parent reply other threads:[~2005-10-31 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 17:57 any fairness in NTPL pthread mutexes? Christopher Friesen
2005-10-31 18:06 ` Lee Revell [this message]
2005-10-31 22:09 ` Lee Revell
2005-10-31 19:09 ` Joe Seigh
2005-11-02 17:47 ` James Courtier-Dutton
2005-11-02 18:47 ` Lee Revell
[not found] <53M7O-7Se-33@gated-at.bofh.it>
2005-11-01 3:52 ` Robert Hancock
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=1130781965.32101.63.camel@mindpipe \
--to=rlrevell@joe-job.com \
--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.