From: Primiano Tucci <p.tucci@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: rostedt@goodmis.org, linux-kernel@vger.kernel.org,
tglx <tglx@linutronix.de>, Bjoern Brandenburg <bbb@email.unc.edu>
Subject: Re: Considerations on sched APIs under RT patch
Date: Thu, 22 Apr 2010 21:33:06 +0200 [thread overview]
Message-ID: <t2uc5b2c05b1004221233z4f071c31ia9b2be2dde72cf96@mail.gmail.com> (raw)
In-Reply-To: <1271953686.1776.372.camel@laptop>
Hi Peter,
It is not in my intents to start a flame, but, as you pointed out
yourself, EDF is not so common, particularly in commercial RTOSes as
you stated (and xnu, indeed, does not fall into this category).
It is not surprisingly that the citation you found was from Mr
Brandenburg and Mr. Anderson from North Carolina University,
incidentally I had a copy of their paper (On the Implementation of
Global RT Schedulers) at the time of reading your message. I think
they're are among the few that concretely and deeply investigated on
G-EDF.
As you could read by Brandenburg and Anderson, there isn't a
standard/reference implementation of Global EDF, but a alot of
"variants" are possible (e.g., event-driven / tick driven promotion,
dedicated/global interrupt handling, typology of data structures and
locking methods ...).
My intent is not to make a form of top ten best kernel award, all we
are trying to do is investigating on the various facilities offered by
the RT operating systems in order to determine how much we can rely on
them.
>> It is how it is implemented now, and how it works under VXWorks!
>
> But that does not, and can not, provide proper isolation and bandwidth
> guarantees since there could be runnable tasks outside the scope of the
> middleware.
Actually our implementation in VxWorks is based on kernel space tasks
that have the maximum priority on the system, even greater of VxWorks
system tasks (that have been shifted down after long and fruitful
support discussions with windriver) therefore no task (except from
interrupt service routines that are accurately weighted under VxWorks)
can alter our middleware. Actually it is controlling real world (yet
not production stage) manufacturing systems, and it is a bit more than
just a play-game.
We are trying to study and understand if, and how, analogous things
can be done on other Real Time Operating Systems.
We choiced posix threads as a start point on linux kernel to verify
the feasibility of the same approach, without intervening too deep on
the kernel.
Thanks again for your interventions!
--
Primiano Tucci
http://www.primianotucci.com
next prev parent reply other threads:[~2010-04-22 19:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 20:48 Primiano Tucci
2010-04-20 9:20 ` Peter Zijlstra
2010-04-20 21:56 ` Primiano Tucci
2010-04-20 23:00 ` Steven Rostedt
2010-04-21 5:16 ` Primiano Tucci
2010-04-21 8:49 ` Peter Zijlstra
2010-04-21 12:46 ` Steven Rostedt
2010-04-21 19:24 ` Primiano Tucci
2010-04-21 19:57 ` Peter Zijlstra
2010-04-21 20:38 ` Primiano Tucci
2010-04-21 20:58 ` Peter Zijlstra
2010-04-22 13:20 ` Steven Rostedt
2010-04-22 13:50 ` Primiano Tucci
2010-04-22 13:57 ` Peter Zijlstra
2010-04-22 15:40 ` Primiano Tucci
2010-04-22 16:28 ` Peter Zijlstra
2010-04-22 17:48 ` Bjoern Brandenburg
2010-04-22 19:33 ` Primiano Tucci [this message]
2010-04-21 12:56 ` Peter Zijlstra
2010-04-27 13:18 ` Thomas Gleixner
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=t2uc5b2c05b1004221233z4f071c31ia9b2be2dde72cf96@mail.gmail.com \
--to=p.tucci@gmail.com \
--cc=bbb@email.unc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.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
all inboxes | Powered by JetHome®