|| ||Peter Zijlstra <peterz-AT-infradead.org> |
|| ||Harald Gustafsson <hgu1972-AT-gmail.com> |
|| ||Re: periods and deadlines in SCHED_DEADLINE |
|| ||Sat, 10 Jul 2010 20:31:50 +0200|
|| ||Raistlin <raistlin-AT-linux.it>,
Song Yuan <song.yuan-AT-ericsson.com>,
Dmitry Adamushko <dmitry.adamushko-AT-gmail.com>,
Thomas Gleixner <tglx-AT-linutronix.de>,
Nicola Manica <nicola.manica-AT-disi.unitn.it>,
Luca Abeni <lucabe72-AT-email.it>,
Claudio Scordino <claudio-AT-evidence.eu.com>,
Harald Gustafsson <harald.gustafsson-AT-ericsson.com>,
Bjoern Brandenburg <bbb-AT-email.unc.edu>, bastoni-AT-cs.unc.edu,
Giuseppe Lipari <lipari-AT-retis.sssup.it>|
|| ||Article, Thread
On Sat, 2010-07-10 at 19:19 +0200, Harald Gustafsson wrote:
> 2010/7/9 Peter Zijlstra <email@example.com>:
> > One thing we could do, although this would make the proposed scheduler a
> > wee bit more complex, is split between hard and soft realtime. Only
> > accept P==rel_D for hard, and schedule the soft tasks in the hard slack
> > or something like that.
> > That way we can later extend the hard admission tests to accept more.
> Sorry for jumping in a bit late. I'm not that happy with this
> suggestion if I understand you correctly. The main reason for having
> deadlines shorter than the periods is for tasks that need a short
> response time and likely are most important for the system to be
> scheduled as fast as possible. Hence if they get scheduled after the
> tasks with deadline=period then that defeat the purpose with having a
> short deadline. Quite often these tasks are short and hence only need
> a low bandwidth, i.e. long period between activations relative to
> deadline and runtime.
> Did I get your proposal correct? Do you agree that tasks that need to
> set a deadline < period usually do that since they need to be
> scheduled in quickly?
Sure, but 'quickly' doesn't convey whether its soft or hard RT you're
interested in. The soft scheme would still have a bound on the tardiness
and is quite sufficient for a large number of workloads (but of course
there are plenty hard workloads too).
> But also other use cases exist with longer running tasks (e.g. around
> 5-10 ms) per period (e.g. around 20 ms). You might have several of
> such tasks running, but as a system designer you know that their
> activation phase will allow them to be scheduled interleaved. This can
> be for example you know that the interrupt pattern waking the tasks
> are interleaved. The admission test would be even more complex if we
> also need to take into account the phases of task periods. Hence I
> think some of these things need to be left for the system designer
> without being hindered by an admission into the highest hard deadline
> scheduling policy. As you might have understood I'm mostly talking
> about embedded system, which have some tasks that are central parts of
> the running system but which also might in parallel run more generic
That is a very delicate point, the whole reason SCHED_FIFO and friends
suck so much is that they don't provide any kind of isolation, and thus,
as an Operating-System abstraction they're an utter failure.
If you take out admission control you end up with a similar situation.
In general the sporadic task model schedulers don't need to be
privileged because it does provide isolation. But the moment you allow
by-passing the admission control everything goes out the window. So even
a simple privileged flag telling the admission control to stuff it would
render the whole system unusable, you'd have to start failing everything
not having that flag, simply because the admission control is rendered
So I would like to take the stand that the mainline scheduler will not
allow such a knob and people will have to help out with improving the
Embedded people can of course easily hack in whatever they well fancy,
and adding the 'yes_I_really_want_this_anyway' flag or even taking out
admission control all together is something the GPL allows them to do.
to post comments)