public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: R Vamshi Krishna <vamshi@cse.iitb.ac.in>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Fabian Scheler <fabian.scheler@gmail.com>,
	     ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Hard-Realtime behaviour
Date: Tue, 30 May 2006 09:25:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.61.0605301431510.22231@mars.cse.iitb.ac.in> (raw)
In-Reply-To: <20060530081637.GH2876@lunn.ch>


Continuing on the discussion, doesn't pipelining on modern processors add 
to our woes. Because then we cannot really determine if a particular 
instruction is going to 'x' cycles or 'y' cycles.


eCos does support disabling instruction and data caches, but is there any 
way that I can disable pipelines in a microprocessor. For example i386ex.


@Andrew : As we have seen most of what is necessary for hard realtime 
behaviour of eCos already is implemented. Can you help me in figuring out 
what is it that is missing that makes eCos soft real-time.


On Tue, 30 May 2006, Andrew Lunn wrote:

> On Tue, May 30, 2006 at 10:09:21AM +0200, Fabian Scheler wrote:
>>> Disable the caches. How long something takes to execute will depend on
>>> what is in the cache. If the code to be executed is still in the cache
>>> from the last time it was executied, it will execute a lot quicker
>>> than if it has to be fetches from RAM/ROM. The same applies to the
>>> data to be processed. So to be deterministic, you need to disable
>>> caches.
>>
>> In order to guarantee deadlines, the worst case has to be
>> deterministic, not the average case! In event-driven systems
>> everything should be fine as long as your worst case response time is
>> beneath your deadline, things get problematic when you use
>> time-discrete algorithms, of course, but in this case you are better
>> of using a time-driven approach, anyway.
>
> So you at least need to disable caches when you determine what the
> worst case is, assuming the cache is actually helping you.
>
>      Andrew
>
>
>

-- 
Regards,
Vamshi

-------------------------------------------------
R.Vamshi Krishna,
M.Tech. CSE (II year),
IIT Bombay
Room no. 320, A-wing, Hostel-12
Mobile : +919869781633
-------------------------------------------------

Yesterday is a past, tomorrow is a future , today is a gift that's why it's called 'present'

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

  reply	other threads:[~2006-05-30  9:25 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
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 [this message]
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=Pine.LNX.4.61.0605301431510.22231@mars.cse.iitb.ac.in \
    --to=vamshi@cse.iitb.ac.in \
    --cc=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=fabian.scheler@gmail.com \
    /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).