Static allocation and lightweight idle tasks #323
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RichardBarry
requested changes
May 12, 2021
|
/bot run checks |
dan4thewin
approved these changes
May 13, 2021
laroche
pushed a commit
to laroche/FreeRTOS-Kernel
that referenced
this pull request
Apr 18, 2024
…reeRTOS#323) * Submodule PKCS FreeRTOS#11. * Add PKCS FreeRTOS#11 demos.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This change adds static allocation for all tasks. It also creates an idle task for each core. The first idle task is the same as the legacy idle task and performs housekeeping and calls the vApplicationIdleHook() function. The remaining idle tasks are very light and only call taskYield if needed.
If static allocation is enabled, the first idle task will call the task allocator just like it has always done. But each additional idle task will have the minimum stack memory (configMINIMAL_STACK_SIZE) statically allocated from within the start scheduler function.
Test Steps
This was tested with the XMOS port with 1, 3 and 7 cores active.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.