From: "Carlos O'Donell" <carlos@redhat.com>
To: Siddhesh Poyarekar <siddhesh.poyarekar@gmail.com>
Cc: Stanislav Meduna <stano@meduna.org>,
libc-help <libc-help@sourceware.org>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: malloc/free and priority inheritance?
Date: Thu, 04 Apr 2013 10:53:44 -0400 [thread overview]
Message-ID: <515D93F8.5050006@redhat.com> (raw)
In-Reply-To: <CAAHN_R1zLdHqpC4JGxjJtADRWGA0hC=G2C3=0Z21KTKk5HJNtg@mail.gmail.com>
On 04/04/2013 09:37 AM, Siddhesh Poyarekar wrote:
> On 4 April 2013 19:00, Stanislav Meduna <stano@meduna.org> wrote:
>
>> hm well.. the assembler version of e.g. __pthread_cond_broadcast
>> in 2.17 for x86 seems to be using the PI. No luck with ARM (2.16
>> in ports) though.
>
> The generic C code was updated to use PI in current master (I don't
> remember if the arm support bits were added, but they must have been
> by now), so you could cherry-pick and backport those bits for your
> distro if you want.
... and ARM uses the generic C code.
My comments in BZ#12114 still remain. Why can't we make malloc/free
use PI locks? We need not convert lll_lock, but just make malloc-machine.h
use a PI-aware lock?
Cheers,
Carlos.
[1] http://sourceware.org/bugzilla/show_bug.cgi?id=12114
next prev parent reply other threads:[~2013-04-04 14:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 23:06 malloc/free and priority inheritance? Stanislav Meduna
2013-04-04 12:59 ` Stanislav Meduna
2013-04-04 13:30 ` Stanislav Meduna
2013-04-04 13:37 ` Siddhesh Poyarekar
2013-04-04 14:53 ` Carlos O'Donell [this message]
2013-04-04 15:32 ` Siddhesh Poyarekar
2013-04-06 14:24 ` Carlos O'Donell
2013-04-04 15:09 ` Stanislav Meduna
2013-04-04 15:39 ` Siddhesh Poyarekar
2013-04-05 17:39 ` Darren Hart
2013-04-06 14:27 ` Carlos O'Donell
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=515D93F8.5050006@redhat.com \
--to=carlos@redhat.com \
--cc=libc-help@sourceware.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=siddhesh.poyarekar@gmail.com \
--cc=stano@meduna.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.