|Data structure parameters for creating the rtprio thread. More...|
|Data structure passed to the application's rtprio thread call back function. More...|
|Results of rtprio thread creation passed back the rtprio thread creater. More...|
|Data structure parameters for creating the rtprio thread. |
|Data structure passed to the application's rtprio thread call back function. |
|Results of rtprio thread creation passed back the rtprio thread creater. |
|typedef void *(*||msp_rtprio_thread_t )(msp_rtprio_thread_args_t *)|
|Syntax for the rtprio thread handler function. |
|int||msp_rtprio_thread_create (int cpu_num, msp_rtprio_thread_t rtprio_thread_func, msp_rtprio_thread_params_t *thread_params_in, msp_rtprio_thread_result_t *thread_result)|
|Install a rtprio thread on a hardware thread. |
|int||msp_rtprio_thread_cancel (msp_rtprio_thread_result_t *thread_result)|
|Cancels a rtprio thread. |
The msp rtprio threads are tied to one of the user CPUS on the ms-pic. They are created with SCHED_FIFO scheduling policy, and can not be preemted by the scheduler while running. There may be more than one rtprio threads attached to the same user core thread. The downside is the user application has to define, yield points while running on the context of the rtprio thread, to avoid performance penalty for other rtprio threads running on the same user CPU.
Cancels a rtprio thread.
This API stops a rtprio thread tied to a user hardware thread The User CPU information will be updated accordingly, for scheduling other rtprio threads.
Install a rtprio thread on a hardware thread.
This API intalls a rtprio thread Loop(rtprio_thread) on a user hardware thread
o A pthread which actually runs the "thread".
o The above pthread is bound to a user hardware thread
o It runs with SCHED_FIFO scheduling policy, with min priority set
All the above will automatically be taken care by the rtprio thread creation APIs.