From: Bill Huey (hui) <billh@gnuppy.monkey.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Arjan van de Ven <arjan@infradead.org>,
"Bill Huey (hui)" <billh@gnuppy.monkey.org>
Subject: Re: [patch 00/10] PI-futex: -V1
Date: Sat, 25 Mar 2006 20:54:04 -0800 [thread overview]
Message-ID: <20060326045404.GA9308@gnuppy.monkey.org> (raw)
In-Reply-To: <20060325184528.GA16724@elte.hu>
On Sat, Mar 25, 2006 at 07:45:28PM +0100, Ingo Molnar wrote:
> We are pleased to announce "lightweight userspace priority inheritance"
> (PI) support for futexes. The following patchset and glibc patch
> implements it, ontop of the robust-futexes patchset which is included in
> 2.6.16-mm1.
...
> Priority Inheritance - why, oh why???
> -------------------------------------
...
> The longer reply:
> -----------------
[comments on app usages of priority inheritance deleted]
You'll need to do priority ceiling emulation as well. I've been using that in an
application as a manual means of preventing preemption of key critical sections,
like a spinlock/preempt_disable(), to prevent priority inversion from happening.
Raising the priority of threads using that lock/critical section is a pretty
effective means of partitioning program logical sections of the application into
threads that are higher and lower priority than the resource. It's cool stuff.
bill
next prev parent reply other threads:[~2006-03-26 4:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-25 18:45 [patch 00/10] PI-futex: -V1 Ingo Molnar
2006-03-26 4:54 ` Bill Huey [this message]
2006-03-26 7:45 ` Ingo Molnar
2006-03-26 9:52 ` Esben Nielsen
2006-03-26 14:25 ` Ingo Molnar
2006-03-26 23:10 ` Bill Huey
2006-03-26 23:47 ` Bill Huey
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=20060326045404.GA9308@gnuppy.monkey.org \
--to=billh@gnuppy.monkey.org \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@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