From: Ingo Molnar <mingo@elte.hu>
To: david singleton <dsingleton@mvista.com>
Cc: robustmutexes@lists.osdl.org, linux-kernel@vger.kernel.org
Subject: Re: robust futex heap support patch
Date: Sat, 26 Nov 2005 14:31:37 +0100 [thread overview]
Message-ID: <20051126133137.GA9722@elte.hu> (raw)
In-Reply-To: <2F3CDB0C-5E50-11DA-8242-000A959BB91E@mvista.com>
* david singleton <dsingleton@mvista.com> wrote:
> There is a new patch, patch-2.6.14-rt15-rf1, that adds support for
> robust and priority inheriting pthread_mutexes on the 'heap'.
we need to go a bit slower. For now i had to remove robust-futexes from
the -rt17 release because they broke normal (non-robust) futex support
in -rt15. A simple mozilla startup would hang... Please send fixes
against -rt16 and i'll try to re-add the robust futexes patch later on.
You can find -rt16 at:
http://people.redhat.com/mingo/realtime-preempt/older/patch-2.6.14-rt16
> The previous patches only supported either file based pthread_mutexes
> or mmapped anonymous memory based pthread_mutexes. This patch allows
> pthread_mutexes to be 'malloc'ed while using the
> PTHREAD_MUTEX_ROBUST_NP attribute or PTHREAD_PRIO_INHERIT attribute.
>
> The patch can be found at:
>
> http://source.mvista.com/~dsingleton
this patch looks much cleaner than the earlier one, but there's one more
step to go: now that we've got the futex_head in every vma, why not hang
all robust futexes to the vma, and thus get rid of ->robust_list and
->robust_sem from struct address_space?
Ingo
next prev parent reply other threads:[~2005-11-26 13:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-26 7:42 david singleton
2005-11-26 13:31 ` Ingo Molnar [this message]
2005-11-26 20:51 ` david singleton
2005-12-05 22:30 ` Esben Nielsen
2005-12-06 4:51 ` david singleton
2005-12-06 14:06 ` Esben Nielsen
2005-12-06 15:23 ` david singleton
2005-12-07 1:23 ` Randy.Dunlap
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=20051126133137.GA9722@elte.hu \
--to=mingo@elte.hu \
--cc=dsingleton@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robustmutexes@lists.osdl.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
all inboxes | Powered by JetHome®