Download v6.0 TASKING Real-Time Operating System
Transcript
Chapter 13. Implementation Parameters The implementation parameters provide detailed information concerning the functionality, performance and memory demand. From the implementation parameters you can obtain valuable information about the impact of the RTOS on your application. 13.1. Introduction From the implementation parameters you can obtain valuable information regarding the impact of the RTOS on your application. There are three kinds of implementation parameters: • Functionality Implementation Parameters. They relate to the configuration of the system. You should always take them into account when writing your application. • Hardware Resources Implementation Parameters. They evaluate the impact of having a RTOS on the hardware resources of the system (RAM, ROM, interrupts, times, etc). • Performance Implementation Parameters. They measure the real time response of the RTOS. The basic conditions to reproduce the measurement of those parameters are mentioned. 13.2. Functionality Implementation Parameters Parameter Description Implementation MAX_NO_TASK Maximum number of tasks. Limits the total number of TASK OIL objects in the OIL file. 126 One task is reserved for the system idle task MAX_NO_ACTIVE_TASK Maximum number of active tasks 127 (i.e. not suspended) in the system. The most general scenario is when all tasks can be 'active' at any given time, thus all having a stack of their own. MAX_NO_PRIO_LEVEL Maximum number of physical priority levels. Limits the total number of TASK OIL objects with different PRIORITY value. 126 The total number of physical priority levels is calculated by the TOC tool after processing the application OIL file. MAX_TASK_PER_LEVEL Maximum number of tasks per priority level. 126 The implementation supports the general case, thus allowing many ready task in the same priority level. However, better performance is achieved when no more than one task is assigned statically to the same priority level (smaller context switch latency times). 125