From: "Fabian Scheler" <fabian.scheler@gmail.com>
To: "R Vamshi Krishna" <vamshi@cse.iitb.ac.in>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Hard-Realtime behaviour
Date: Mon, 29 May 2006 16:26:00 -0000 [thread overview]
Message-ID: <69dd805e0605290926m745c0cf2yc19b9fd400e7fa9b@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0605291751420.14208@mars.cse.iitb.ac.in>
> IFAIK a "Hard" real-time OS is an Operting System in which the worst-case
> execution time of the system calls is either known beforehand or
> computable based on the how the application is configured (aka no. of
> threads, no. of interrupting sources, their periodicity) etc.. but I have
> not been successful.
you have not been successful regarding what? - to show that all parts
of the kernel API have deterministic behaviour or are suitable for a
use in hard real-time systems? Which ones? Maybe you should restrict
the usage of the kernel API to achive hard real-time compliance (e.g.
abstaining the processor voluntarily makes the analysis of any
real-time system nasty!!) ?
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
next prev parent reply other threads:[~2006-05-29 16:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 16:09 R Vamshi Krishna
2006-05-29 16:26 ` Fabian Scheler [this message]
2006-05-29 21:16 ` Wolfgang Köbler
2006-05-30 5:13 ` R Vamshi Krishna
2006-05-30 7:53 ` Andrew Lunn
2006-05-30 8:09 ` Fabian Scheler
2006-05-30 8:16 ` Andrew Lunn
2006-05-30 9:25 ` R Vamshi Krishna
2006-05-30 11:12 ` Andrew Lunn
[not found] ` <Pine.LNX.4.61.0 606031953120.6382@mars.cse.iitb.ac.in>
[not found] ` <Pine.LNX.4.61.0 606031953120.6382@mars.cse.iitb.ac.in>
[not found] ` <"Pine.LNX.4.61 .0 606031953120.6382"@mars.cse.iitb.ac.in>
[not found] ` <Pine.LNX.4.61.0606040253350.26447@m ars.cse.iitb.ac.in>
2006-06-03 16:26 ` R Vamshi Krishna
2006-06-03 20:13 ` Roy E Richardson
2006-06-03 21:31 ` R Vamshi Krishna
[not found] ` <003401c6885d $23027ee0$070fe644@EngAtPlayWS>
[not found] ` <003401c6885d $23027ee0$070fe644@EngAtPlayWS>
[not found] ` <003401c6885d$23027ee0$070fe644@EngAtPlayWS>
2006-06-18 22:21 ` R Vamshi Krishna
2006-06-18 23:31 ` John Carter
2006-06-18 23:46 ` R Vamshi Krishna
2006-06-19 0:27 ` John Carter
2006-05-30 11:15 ` Andrew Lunn
2006-05-30 14:44 ` Enno Luebbers
2006-05-30 9:34 ` Nils Labugt
2006-05-30 10:37 ` Fabian Scheler
2006-05-30 11:21 ` Luis Friedrich
2006-05-30 11:47 ` Fabian Scheler
2006-05-30 12:48 ` R Vamshi Krishna
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=69dd805e0605290926m745c0cf2yc19b9fd400e7fa9b@mail.gmail.com \
--to=fabian.scheler@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
--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).