Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
07/09/10 14:41
Read: times


 
#177192 - re - Separate display processor
Responding to: ???'s previous message
Per Westermark said:
It is similar to all RT problems. Even when you have an RTOS, your problem is to write a program that can use as small processor as possible while still guaranteeing worst-case performance. The seldom happening worst-case scenarios often require you to buy a processor where most of the time is wasted doing nothing.

Having fixed time slices just means that every time slice has a hard wost-case time to get the work done. Using a generic RTOS, background tasks can play with spare processing capacity but hard-to-test and hard-to-prove peak loads means you may have to select a processor that has way more time available for background tasks than you have a need for.

Exactly. The board design wasn't mine. I just have to make it work. Times lices cannot be too short for the longer routines, then a time slice that only polls a hardware pin is such a waste.
That is what I am aim to overcome.
Thanks
Regards
Johan Smit

List of 23 messages in thread
TopicAuthorDate
co-operative scheduler            01/01/70 00:00      
   RE: This inevitably wastes processing time.            01/01/70 00:00      
      re - Separate display processor            01/01/70 00:00      
         I see (I think)            01/01/70 00:00      
            re - Separate display processor            01/01/70 00:00      
   Separate display processor?            01/01/70 00:00      
      re - Separate display processor            01/01/70 00:00      
   how can processing "waste processing time"            01/01/70 00:00      
      Answered here?            01/01/70 00:00      
      All multi-tasking with real-time requiremens suffer waste            01/01/70 00:00      
         re - Separate display processor            01/01/70 00:00      
            Parasitic newspapers?            01/01/70 00:00      
   I do not know your "Time Triggered Prioritised Cooperative S            01/01/70 00:00      
      re - Separate display processor            01/01/70 00:00      
         what does a time interval have to do with it?            01/01/70 00:00      
         TTPCS            01/01/70 00:00      
            re- TTPCS            01/01/70 00:00      
   No need for these canned "schedulers"            01/01/70 00:00      
      re - real time system            01/01/70 00:00      
         no, it does not            01/01/70 00:00      
            re- Scheduler            01/01/70 00:00      
      Timeslice timewaste            01/01/70 00:00      
         re - real time system            01/01/70 00:00      

Back to Subject List