From: Peter Zijlstra <peterz@infradead.org>
To: "Stephan Bärwolf" <stephan.baerwolf@tu-ilmenau.de>
Cc: linux-kernel@vger.kernel.org, Nikhil Rao <ncrao@google.com>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: sched: fix/optimise some issues
Date: Thu, 21 Jul 2011 18:51:48 +0200 [thread overview]
Message-ID: <1311267108.29152.178.camel@twins> (raw)
In-Reply-To: <4E28557A.7040704@tu-ilmenau.de>
On Thu, 2011-07-21 at 18:36 +0200, Stephan Bärwolf wrote:
> I also remember weak Linus had sth. against "priority inheritance"
> (don't ask me what or why - I don't know),
> but it would be an honour to me working with you guys to implement
> this feature in future kernels.
Look at kernel/rt_mutex.c, it as a complete tradition Priority
Inheritance implementation :-)
The trouble is that it only works for SCHED_FIFO/RR.
Now you can extend PI to cover weighted fair queueing, or implement the
much simpler proxy execution policy which generalizes to pretty much any
scheduling algorithm, see for example the paper: "Timeslice donation in
component-based systems" in:
http://www.artist-embedded.org/docs/Events/2010/OSPERT/OSPERT2010-Proceedings.pdf
Extending that to SMP is the 'interesting' bit..
However that will not solve the true idle thing since some
synchronization primitives we have are fundamentally incompatible with
any form of PI (including the various ceiling protocols) :-/, see for
example the traditional semaphore and completions.
prev parent reply other threads:[~2011-07-21 16:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 13:42 sched: fix/optimise some issues Stephan Bärwolf
2011-07-20 19:11 ` Peter Zijlstra
2011-07-21 1:00 ` Mike Galbraith
2011-07-20 19:11 ` Peter Zijlstra
2011-07-20 19:11 ` Peter Zijlstra
2011-07-21 15:08 ` Peter Zijlstra
2011-07-21 16:36 ` Stephan Bärwolf
2011-07-21 16:32 ` Peter Zijlstra
2011-07-21 16:43 ` Peter Zijlstra
2011-07-21 16:51 ` Peter Zijlstra [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=1311267108.29152.178.camel@twins \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=ncrao@google.com \
--cc=stephan.baerwolf@tu-ilmenau.de \
/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