HTTP Server: Added ability to select core (IDFGH-774) #3190
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.
Feature
The HTTP server task can now be pinned to a particular core.
Example Application
In our application one core is dedicated to driving a speaker. If the HTTP server runs on the same core as the task controlling the speaker, the speaker stutters when the device receives and HTTP request while operating the speaker. By moving the server to a different core, the stutter is eliminated.
Notes
The core is set to tskNO_AFFINITY in the default macro
This is a duplicate of #3137 due to a git merge issue.