Add pollable state definitions into tcp state machine #1
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.
This adds in just the pollable state definitions to the TCP states. We do this by defining the pollable state for each TCP state, and therefore this is what justifies the
complete
states (formerlyready
).It also fits quite well into the TCP state machine because the
would-block
transition is clearly defined as well.Even without these states, I would strongly encourage a clear specification of the pollable resolution state for all states of the TCP machine in whatever form, this is just the way I found to do it.