This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Hard-Realtime behaviour
- From: "Fabian Scheler" <fabian dot scheler at gmail dot com>
- To: "R Vamshi Krishna" <vamshi at cse dot iitb dot ac dot in>
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Mon, 29 May 2006 18:26:20 +0200
- Subject: Re: [ECOS] Hard-Realtime behaviour
- References: <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