From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: robust mutex support
Date: Thu, 17 Mar 2016 23:43:22 -0400 [thread overview]
Message-ID: <20160318034322.GL21636@brightrain.aerifal.cx> (raw)
In-Reply-To: <F1A3FD1C-9053-4BAD-B111-92928D40F0F5@gmail.com>
On Thu, Mar 17, 2016 at 06:28:31PM -0700, Khem Raj wrote:
> Hi All,
>
> We are missing robust mutexes in musl, there are packages which depend on them, one of
> the package that I ran across recently is apache portable runtime ( apr ) as well as
> linux rt-tests package. There might be more, but I think its a desirable feature to have
>
> Thoughts?
I think you mean priority inheritance. musl has had robust mutex
support since roughly a month after the initial release in 2011. :)
Rich
next prev parent reply other threads:[~2016-03-18 3:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 1:28 Khem Raj
2016-03-18 3:43 ` Rich Felker [this message]
2016-03-18 3:49 ` Khem Raj
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=20160318034322.GL21636@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).