public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Fabian Scheler <fabian.scheler@gmail.com>
To: R Vamshi Krishna <vamshi@cse.iitb.ac.in>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS]: Is eCos Hard Real Time OS ??
Date: Fri, 24 Jun 2005 19:52:00 -0000	[thread overview]
Message-ID: <69dd805e050624125228f3b7c0@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0506241630130.20838@mars.cse.iitb.ac.in>

Hi,

I somehow have the feeling, that you have a somehow strange opinion
about what you call "hard real time systems", so what is a hard real
time system?

Well, the general understanding of a hard real time systems is that is
has to fulfill some tasks which underlie hard timing constraints
called deadlines. These deadlines must be guaranteed under all
circumstances otherwise the whole system fails.

But these tasks (these tasks do not directly correspond to threads or
processes!) are part of the whole real time system, t.m. of an
application, an operating system just provides an infrastructure to
execute this application. Deadlines now have to be guaranteed within
the application, not within the operating system, as these deadlines
are application specific! How should an operating system guarantee the
deadline of such a task? You have to analyze the whole application and
make sure that every task completes in time by some kind of formal
technique (WCET, scheduling theory ...).

The most important property of an RTOS is determinism, so you can such
formal techniques and verify your system. OK, some operating systems
do not provide an infrastructure that is suitable for building real
time systems,of course (eg. Windows, Linux ...), but eCos does.

At least: they way you are describing your requirements seems like you
are going to build a time triggered real time system, maybe eCos is
not the best choice here. eCos is better for designing event triggered
systems.

Ciao, Fabian

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

      parent reply	other threads:[~2005-06-24 19:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24 11:07 R Vamshi Krishna
2005-06-24 11:27 ` Andrew Lunn
2005-06-24 11:41   ` R Vamshi Krishna
2005-06-24 12:32     ` Kozo Kakehi
2005-06-24 12:54       ` R. Vamshi Krishna
2005-06-24 12:38     ` Andrew Lunn
2005-06-24 12:52       ` R. Vamshi Krishna
2005-06-24 13:32         ` Andrew Lunn
2005-06-24 19:52 ` Fabian Scheler [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=69dd805e050624125228f3b7c0@mail.gmail.com \
    --to=fabian.scheler@gmail.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=vamshi@cse.iitb.ac.in \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).