From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31319 invoked by alias); 29 May 2006 16:09:24 -0000 Received: (qmail 31230 invoked by uid 22791); 29 May 2006 16:09:23 -0000 X-Spam-Check-By: sourceware.org Received: from smtp1.iitb.ac.in (HELO smtp1.iitb.ac.in) (59.163.25.49) by sourceware.org (qpsmtpd/0.31) with SMTP; Mon, 29 May 2006 16:09:20 +0000 Received: (qmail 24667 invoked from network); 29 May 2006 18:02:09 +0530 Received: from unknown (HELO ldns2.iitb.ac.in) (10.200.12.2) by smtp1.iitb.ac.in with SMTP; 29 May 2006 18:02:09 +0530 Received: (qmail 2795 invoked by uid 509); 29 May 2006 12:32:09 -0000 Received: from 10.105.1.1 by ldns2 (envelope-from , uid 501) with qmail-scanner-1.25st (clamdscan: 0.88/1495. spamassassin: 3.1.0. Clear:RC:1(10.105.1.1):. Processed in 0.01648 secs); 29 May 2006 12:32:09 -0000 Received: from unknown (HELO cse.iitb.ac.in) (10.105.1.1) by ldns2.iitb.ac.in with SMTP; 29 May 2006 12:32:09 -0000 Received: (qmail 28564 invoked by uid 11940); 29 May 2006 12:38:15 -0000 Received: from 10.105.1.11 by jeeves.cse.iitb.ac.in (envelope-from , uid 11926) with qmail-scanner-1.25 (clamdscan: 0.87/1494. spamassassin: 3.1.0. Clear:RC:1(10.105.1.11):. Processed in 0.031692 secs); 29 May 2006 12:38:15 -0000 Received: from mars.cse.iitb.ac.in ([10.105.1.11]) (envelope-sender ) by cse.iitb.ac.in (qmail-ldap-1.03) with SMTP for ; 29 May 2006 12:38:15 -0000 Date: Mon, 29 May 2006 16:09:00 -0000 From: R Vamshi Krishna To: ecos-discuss@ecos.sourceware.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: [ECOS] Hard-Realtime behaviour X-SW-Source: 2006-05/txt/msg00228.txt.bz2 I am currently working on making eCos hard-real time. As the developers of RTAI claim that RTAI is hard-realtime, I have been comparing the code of RTAI and eCos w.r.t the interrupt handling, kernel primitives, system calls etc. 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. I would be really glad if someone could help in this direction. I would like to know what parts of eCos have to be either re-written or written from scratch to conform to hard-realtime OS behavious. Thanking in Advance. PS : I understand that I have asked the same question once too many, but I am only askeing after trying out all other avenues. -- Regards, Vamshi -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss