This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: malloc/free and priority inheritance?
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Siddhesh Poyarekar <siddhesh dot poyarekar at gmail dot com>
- Cc: Stanislav Meduna <stano at meduna dot org>, libc-help <libc-help at sourceware dot org>, "linux-rt-users at vger dot kernel dot org" <linux-rt-users at vger dot kernel dot org>
- Date: Thu, 04 Apr 2013 10:53:44 -0400
- Subject: Re: malloc/free and priority inheritance?
- References: <515B647C dot 3080505 at meduna dot org> <515D7943 dot 5000401 at meduna dot org> <515D808C dot 8090808 at meduna dot org> <CAAHN_R1zLdHqpC4JGxjJtADRWGA0hC=G2C3=0Z21KTKk5HJNtg at mail dot gmail dot 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