From: Bill Huey (hui) <billh@gnuppy.monkey.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Esben Nielsen <simlo@phys.au.dk>,
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: Sun, 26 Mar 2006 15:47:25 -0800 [thread overview]
Message-ID: <20060326234725.GA15203@gnuppy.monkey.org> (raw)
In-Reply-To: <20060326231000.GA14280@gnuppy.monkey.org>
On Sun, Mar 26, 2006 at 03:10:00PM -0800, Bill Huey wrote:
> On Sun, Mar 26, 2006 at 04:25:39PM +0200, Ingo Molnar wrote:
>
> It's not quite as a simple as that. The use of a ceiling is a more aggressive
> method of controlling priority in an application. The use [of] it can control [-the-]
> thread preeemption, with regard to thread priority, [-primarily-] below the ceiling
> by prevent the occurance of priority inversion and the[re]for[e] the need for simple
> priority inheritance in the first place. It just simplifies what's going on in
> the app as wel[l] as what can happen [if priorities in an app are complex].
[with some grammar and spelling corrections]
Sorry, I think you folks get the idea, but typing a technical email just getting out of bed
without contacts is a bit challenging. :)
bill
prev parent reply other threads:[~2006-03-26 23:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-25 18:45 Ingo Molnar
2006-03-26 4:54 ` Bill Huey
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 [this message]
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=20060326234725.GA15203@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=simlo@phys.au.dk \
--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
Powered by JetHome