FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [May 2016 Threads]
Hi,
i read the scheduler pages but am still confused about if it is always the highest priority task in FreeRTOS that is executing? Or does the scheduler yield the highest priority task to give processing time to others as well?
Regards
By default, configUSETIMESLICING is set to 1, and configUSE_PREEMPTION
is set to 1. When this is the case, the scheduler will always run the
highest priority task that is able to run. A task that is able to run
is a task that is not in the Blocked or Suspended state.
Therefore, if a low priority task is running when a high priority task
becomes able to run, then a switch to the higher priority task will
occur immediately. Also, while a higher priority task is running (is
not in the Blocked or Suspended state) all lower priority tasks will be
starved of processing time - which is why tasks must enter the Blocked
state.
If there is more than one task at any given priority, and that priority
is the highest priority that has any tasks that are able to run, then
the scheduler will time slice the tasks - each time the tick interrupt
occurs it will switch to another task of equal priority.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.