From: Ingo Molnar <mingo@elte.hu>
To: Daniel Walker <dwalker@mvista.com>
Cc: linux-kernel@vger.kernel.org, sdietrich@mvista.com,
rostedt@goodmis.org, inaky.perez-gonzalez@intel.com
Subject: Re: [PATCH] Abstracted Priority Inheritance for RT
Date: Wed, 1 Jun 2005 09:54:14 +0200 [thread overview]
Message-ID: <20050601075414.GA25081@elte.hu> (raw)
In-Reply-To: <1117594659.3798.18.camel@dhcp153.mvista.com>
* Daniel Walker <dwalker@mvista.com> wrote:
> I've abstracted priority inheritance from the RT patch. I created pi.h
> and pi.c that can be used by other structures that need priority
> inheritance. I also added a config option CONFIG_PRIORITY_INHERITANCE
> so that PI can be turned off . This could also be made completely
> separate from the RT patch.
i'd rather not slow things down by callbacks and other abstraction
before seeing how things want to integrate in fact. Do we really need
the callbacks?
Ingo
next prev parent reply other threads:[~2005-06-01 7:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 2:57 [PATCH] Abstracted Priority Inheritance for RT Daniel Walker
2005-06-01 3:35 ` Steven Rostedt
2005-06-01 7:54 ` Ingo Molnar [this message]
2005-06-01 12:57 ` Daniel Walker
2005-06-01 14:07 ` Esben Nielsen
2005-06-01 23:58 ` Daniel Walker
2005-06-02 8:25 ` Esben Nielsen
2005-06-02 15:11 ` Daniel Walker
2005-06-02 15:18 ` Esben Nielsen
2005-06-02 17:31 ` Daniel Walker
2005-06-02 20:27 ` Esben Nielsen
2005-06-02 21:50 ` Daniel Walker
2005-06-03 9:08 ` Esben Nielsen
-- strict thread matches above, loose matches on Subject: below --
2005-06-02 0:10 Perez-Gonzalez, Inaky
2005-06-02 0:25 ` Daniel Walker
2005-06-02 0:52 linux
2005-06-02 1:21 Perez-Gonzalez, Inaky
2005-06-02 1:22 Perez-Gonzalez, Inaky
2005-06-02 5:43 ` john cooper
2005-06-03 0:54 ` Bill Huey
2005-06-03 1:10 ` Sven Dietrich
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=20050601075414.GA25081@elte.hu \
--to=mingo@elte.hu \
--cc=dwalker@mvista.com \
--cc=inaky.perez-gonzalez@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sdietrich@mvista.com \
/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