Interface to the POSIX Priority Implementation.
More...
Interface to the POSIX Priority Implementation.
◆ POSIX_SCHEDULER_MINIMUM_PRIORITY
#define POSIX_SCHEDULER_MINIMUM_PRIORITY (1) |
This is the numerically least important POSIX priority.
◆ _POSIX_Priority_From_core()
Converts the SuperCore priority to the corresponding POSIX API priority.
- Parameters
-
[in] | scheduler | The scheduler instance. |
[in] | priority | The SuperCore priority to convert. |
- Returns
- The corresponding POSIX API priority.
◆ _POSIX_Priority_To_core()
Converts the POSIX API priority to the corresponding SuperCore priority and validates it.
According to POSIX, numerically higher values represent higher priorities. Thus, SuperCore has priorities run in the opposite sense of the POSIX API.
Let N be the maximum priority of this scheduler instance. The SuperCore priority zero is system reserved (PRIORITY_MINIMUM). There are only N - 1 POSIX API priority levels since a thread at SuperCore priority N would never run because of the idle threads. This is necessary because GNAT maps the lowest Ada task priority to the lowest thread priority. The lowest priority Ada task should get to run, so there is a fundamental conflict with having N priorities.
- Parameters
-
[in] | scheduler | The scheduler instance. |
[in] | priority | The POSIX API priority to convert and validate. |
[out] | valid | Indicates if the POSIX API priority is valid and a corresponding SuperCore priority in the specified scheduler instance exists. |
- Returns
- The corresponding SuperCore priority.