Make task priority configurable #98
Open
Conversation
This file contains 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
…t the tasks' priority is (defaults to 3).
avillacis
added a commit
to yubox-node-org/AsyncTCPSock
that referenced
this pull request
Oct 28, 2021
Add config option 'CONFIG_ASYNC_TCP_TASK_PRIORITY', which defines what the tasks' priority is (defaults to 3). Based on me-no-dev/AsyncTCP#98
serek4
added a commit
to serek4/AsyncTCP
that referenced
this pull request
Oct 24, 2023
[pull request 98](me-no-dev#98)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Also referring back to espressif/arduino-esp32#4131.
TCP task priority ought to be configurable, especially with UDP task priority defaulting to the same value. A user may want to take a choice to priorize one over the other, or to have more room for his own vtask priorities below TCP beyond 0-2.