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: Sat, 06 Apr 2013 10:24:02 -0400 [thread overview]
Message-ID: <51603002.1020501@redhat.com> (raw)
In-Reply-To: <CAAHN_R2zdvYwQL_Md8C=+O9w3tc2y+XR5tofv3FEe6CjcOubAQ@mail.gmail.com>
On 04/04/2013 11:32 AM, Siddhesh Poyarekar wrote:
> On 4 April 2013 20:23, Carlos O'Donell <carlos@redhat.com> wrote:
>> ... 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?
>
> The trouble (as always) is to decide on when to use PI-aware locks.
> Do we do that by default or do we have (*chuckle*) an environment
> variable to override the default locks? Maybe this discussion is more
> suitable for libc-alpha though, since we can hopefully get all
> maintainers to chime in there.
The number of tunables just keeps growing doesn't it?
Added this to my list of tunables in the WIP document I'm writing:
sourceware.org/glibc/wiki/TuningLibraryRuntimeBehavior
Cheers,
Carlos.
next prev parent reply other threads:[~2013-04-06 14:25 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
2013-04-04 15:32 ` Siddhesh Poyarekar
2013-04-06 14:24 ` Carlos O'Donell [this message]
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=51603002.1020501@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 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).