LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Dario Faggioli" <firstname.lastname@example.org>
To: "Henrik Austad" <email@example.com>
Cc: "Peter Zijlstra" <firstname.lastname@example.org>,
email@example.com, "Ingo Molnar" <firstname.lastname@example.org>,
"Michael Trimarchi" <email@example.com>,
"Thomas Gleixner" <firstname.lastname@example.org>,
"Steven Rostedt" <email@example.com>,
Subject: Re: Deadline scheduling (was: Re: Rearranging layout of code in the scheduler)
Date: Fri, 31 Oct 2008 19:08:54 +0100 (CET) [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On Gio, 30 Ottobre 2008 10:44 pm, Henrik Austad wrote:
>> As to why I'm
>> looking at EDF, I think the answer to that is a bit too long (and
>> appropriate for this email anyway) so I'll leave that part out.
>> > Well, I understand that, but it could be interesting... At least to
>> > me.
> ok, simply put:
> * give each task a relative deadline (will probably introduce a new
> please don't shoot me).
> * when the task enters TASK_RUNNING, set abosolute deadline to time_now +
> * insert task in rq, sorted by abs_deadline
> * pick leftmost task and run it
> * when task is done, pick next task
> that's it.
Ok, that is how EDF work, and I know it... I was asking something
different... But nevermind! :-D
>> > > The most interesting part of EDF is not the
>> > > actual scheduler itself (although there are fun issues with that as
>> > > well), but extending the Priority Inheritance framework to deal with
>> > > all the fun cases that come with EDF.
> Well, I find EDF intersting because it is so blissfully simple. :-)
I agree, EDF is very simple and has a lot of very nice properties...
Problem is do decide how to assign a deadline to a task, if it is not a
classical soft or hard real-time one! :-O
But you're not talking about things like that, aren't you?
> Yes, well, EDF is not optimal for SMP systems, only for single core.
> you can do a pretty good attempt by assigning tasks to cores in a greedy
> fashion (simply put the next task at the CPU with the lowest load).
I definitely agree that hard real time workloads are better handled by
partitioned EDF, but for soft ones, it was sad to suffer from the possible
CPU utilization loss it entails.
Also, what about resources shared by different tasks in different
CPU/partitions? And if you avoid sharing resources between tasks in
different partitions (is that acceptable?), what about system resources,
that are shared by _all_ tasks in the system by definition?
Sorry about asking so much questions, but these are the issues we are
trying to address, and I'm quite interested in knowing if you have any
idea about them. :-)
> No. You should have *either* FIFO/RR *or* EDF, not both at the same time.
> you absolutely require both, you should at least separate them on a
> basis. If you mix them, they need to be aware of the other in order to
> the right descision, and that is not good.
Well, obvioulsy it's something that we have to think carefully, but I
can't see any harmful situation in having a deadline based and a fixed
priority based scheduling from where to pick task in (sorry) priority
> Well.. why not just treat *all* RT-tasks as *either* FIFO/RR or EDF?
> fifo and edf together will complicate things. And, people looking for edf,
> will not use fifo/rr anyway (famous last words).
Ok, maybe it's a matter of personal feelings, but I think that such a
design, even more complicated, could be very nice and useful.
>> Which leaves us with the big issue of priority inversion ;-)
> Couldn't above idea solve a bit of this? I have some papers on deadline
> inheritance laying aorund somewhere, I can have a look at that, I think it
> was a fairly elegant solution to some of these issues there.
Well, I personally think that partitioning _raises_ issues about resource
sharing instead of lightening them... In an OS like Linux is, at least...
PS. Sorry for the webmail... I'm abroad and I've not my laptop with me :-(
next prev parent reply other threads:[~2008-10-31 18:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 15:34 Rearranging layout of code in the scheduler Henrik Austad
2008-10-28 16:50 ` Peter Zijlstra
2008-10-28 19:41 ` Henrik Austad
2008-10-30 16:49 ` faggioli
2008-10-30 17:17 ` Deadline scheduling (was: Re: Rearranging layout of code in the scheduler) Peter Zijlstra
2008-10-30 17:48 ` Peter Zijlstra
2008-10-30 21:44 ` Henrik Austad
2008-10-31 9:03 ` Peter Zijlstra
2008-10-31 12:09 ` Henrik Austad
2008-10-31 13:30 ` Peter Zijlstra
2008-10-31 15:05 ` Henrik Austad
2008-10-31 18:08 ` Dario Faggioli [this message]
2008-10-31 17:49 ` Dario Faggioli
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--subject='Re: Deadline scheduling (was: Re: Rearranging layout of code in the scheduler)' \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).