Compounds | |
struct | RtecBase::Dependency_Info |
Define dependencies between two RT_Infos. More... | |
Typedefs | |
typedef long | handle_t |
The Event and Scheduling Service need to communicate information about RT_Infos (descriptions about the scheduling properties of a simple operation). More... | |
typedef long | OS_Priority |
Helper typedef to define the OS priority. More... | |
typedef long | Preemption_Priority_t |
Helper typedef to define the OS-independent priority. More... | |
typedef long | Preemption_Subpriority_t |
Helper typedef to define the OS-independent sub-priority. More... | |
Enumerations | |
enum | Dependency_Type_t { ONE_WAY_CALL, TWO_WAY_CALL } |
Specify one-way or two-way call. More... |
These types are defined in a separate module to decouple the real-time event services from the scheduling service interface (and implementation!)
|
The Event and Scheduling Service need to communicate information about RT_Infos (descriptions about the scheduling properties of a simple operation). On a centralized application one would use pointers for such a task, but obviously that does not work on a distributed system. It is tempting to use object references to identify each RT_Info, but that does not work either: first the *contents* of the RT_Info must be transmitted between applications, and object references are not good identifiers (due to the semantics of _is_equivalent()) The handle_t type is used to generate unique identifiers on the scheduling service, the Event Service can then refer to any RT_Info using either their name or the quicker handle_t. |
|
Helper typedef to define the OS priority.
|
|
Helper typedef to define the OS-independent priority.
|
|
Helper typedef to define the OS-independent sub-priority.
|
|
Specify one-way or two-way call.
|