The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Raistlin <raistlin@linux.it>
To: Linus Walleij <linus.ml.walleij@gmail.com>
Cc: Claudio Scordino <claudio@evidence.eu.com>,
	Peter Zijlstra <peterz@infradead.org>,
	michael@evidence.eu.com, mingo@elte.hu,
	linux-kernel@vger.kernel.org, tglx@linutronix.de,
	johan.eker@ericsson.com, p.faure@akatech.ch,
	Fabio Checconi <fabio@gandalf.sssup.it>,
	Dhaval Giani <dhaval.giani@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Tommaso Cucinotta <tommaso.cucinotta@sssup.it>
Subject: Re: [RFC][PATCH] SCHED_EDF scheduling class
Date: Wed, 23 Sep 2009 16:45:15 +0200	[thread overview]
Message-ID: <1253717115.5631.500.camel@Palantir> (raw)
In-Reply-To: <63386a3d0909230708g10aa2911vaa39a6e02530c902@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2289 bytes --]

On Wed, 2009-09-23 at 16:08 +0200, Linus Walleij wrote:
> > With EDF, instead, the test is much easier: if the bandwidth is less than
> > 100%, then you are sure that the deadlines will be met. In other words, you
> > can fully exploit processor bandwidth up to 100% being sure that timing
> > constraints of EDF tasks will be guaranteed.
> 
> This must be under the assumption that all code running in the system
> is preemtible, is it not? Which means, negligible or close to negligible
> non-preemptible code.
> 
Right. Moreover, this also happen only if tasks are independent, do not
share resources, etc. which all are things that do not apply to Linux...
This is more than true!

However, this holds for any scheduler you may decide to consider,
especially if a real-time one.
A scheduling test is always based on a task model and, at least, with a
simple --completely preemptible, independent tasks-- model, EDF is
simpler than other solutions.

Obviously, if the model gets more complicated, more complicated analysis
has to be used, and again, this happen to all the schedulers you will
try to analyze.

> How much as we might like it to be, that is not (yet) the situation
> with the Linux kernel, far off.
> 
> So we will still very much need the CONFIG_PREEMPT_RT patch
> to get closer to that ideal situation, and we still need to get rid of
> the BKL.
> 
Independently from the above, I agree with you here, and in fact a
SCHED_EDF patch on top of PREEMPT_RT will hopefully come shortly, we and
some other guys are already at work on this! ;-P

> Now I ought to write fewer mails and look into solving that little
> problem... You don't happen to know if we can have a EU FP7
> project sponsored to rid out the BKL and switch and test drivers
> en masse to use threaded interrupt handlers do you? ;-)
> 
Well, it's an interesting (applied) research topic, and I think there
still is a call for FP7 EU fundings! :-)

Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
----------------------------------------------------------------------
Dario Faggioli, ReTiS Lab, Scuola Superiore Sant'Anna, Pisa  (Italy)

http://blog.linux.it/raistlin / raistlin@ekiga.net /
dario.faggioli@jabber.org

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-09-23 14:45 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-22 10:30 [RFC][PATCH] SCHED_EDF scheduling class Raistlin
2009-09-22 11:05 ` Peter Zijlstra
2009-09-22 12:51   ` Raistlin
2009-09-22 18:36     ` Peter Zijlstra
2009-09-23 12:19       ` Raistlin
2009-09-23 12:25         ` Dhaval Giani
2009-09-27  6:55       ` Henrik Austad
2009-09-29 16:10         ` Raistlin
2009-09-29 17:34           ` Chris Friesen
2009-09-30 15:58             ` Raistlin
2009-09-30 17:35               ` Chris Friesen
2009-09-22 11:58 ` Claudio Scordino
2009-09-22 12:38   ` Peter Zijlstra
2009-09-24 16:08     ` Claudio Scordino
2009-09-22 13:24 ` Daniel Walker
2009-09-22 14:01   ` Raistlin
2009-09-22 14:02     ` Daniel Walker
2009-09-22 16:42     ` Peter Zijlstra
2009-09-22 19:11       ` Ingo Molnar
2009-09-23  0:51         ` checkpatch as a tool (was Re: [RFC][PATCH] SCHED_EDF scheduling class) Daniel Walker
2009-09-23  1:01           ` Joe Perches
2009-09-23  1:11             ` Daniel Walker
2009-09-23 19:24               ` Andy Isaacson
2009-09-24 14:58                 ` Daniel Walker
2009-09-30 12:06               ` Pavel Machek
2009-09-23 12:22             ` Ingo Molnar
2009-09-23 14:43               ` Daniel Walker
2009-09-30 12:04           ` Pavel Machek
2009-09-23  7:03         ` [RFC][PATCH] SCHED_EDF scheduling class Raistlin
2009-09-23 21:39     ` Steven Rostedt
2009-09-24  0:58       ` GeunSik Lim
2009-09-22 16:38   ` Peter Zijlstra
2009-09-22 23:39   ` Jonathan Corbet
2009-09-22 23:55     ` Daniel Walker
2009-09-23  0:06       ` Jonathan Corbet
2009-09-23  0:40         ` Daniel Walker
2009-09-23 11:46           ` Avi Kivity
2009-09-23 12:25             ` Ingo Molnar
2009-09-23 14:50               ` Daniel Walker
2009-09-23 14:58                 ` Avi Kivity
2009-09-23 15:08                   ` Daniel Walker
2009-09-23 15:12                     ` Avi Kivity
2009-09-23 15:24                       ` Daniel Walker
2009-09-30 12:05                 ` Pavel Machek
2009-09-22 20:55 ` Linus Walleij
2009-09-23 13:00   ` Raistlin
2009-09-23 13:22   ` Claudio Scordino
2009-09-23 14:08     ` Linus Walleij
2009-09-23 14:45       ` Raistlin [this message]
2009-09-23 12:33 ` Linus Walleij
2009-09-23 12:50   ` Linus Walleij
2009-09-23 13:30   ` Raistlin
2009-09-29 18:15     ` roel kluin
2009-09-30 15:59       ` Raistlin
2009-09-24  0:34 ` GeunSik Lim
2009-09-24  6:08   ` Raistlin
2009-09-24  9:11   ` Claudio Scordino

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=1253717115.5631.500.camel@Palantir \
    --to=raistlin@linux.it \
    --cc=claudio@evidence.eu.com \
    --cc=dhaval.giani@gmail.com \
    --cc=fabio@gandalf.sssup.it \
    --cc=johan.eker@ericsson.com \
    --cc=linus.ml.walleij@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@evidence.eu.com \
    --cc=mingo@elte.hu \
    --cc=p.faure@akatech.ch \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=tommaso.cucinotta@sssup.it \
    /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