Add blocking function to block osd thread when CoDel condition is violated #17
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.
When we set the kvQ capacity to 1, we allow 1 reqs to get into the kvQ. For these two lines:
Does it mean that we should get the ten in order 2,1,2,1,2,1.,..?
But I noticed that we could have order 2,1,2,1,1,2,.... Does this mean we have a priority inversion?
If so, we could count the number of inversion.
The result is shown in the
CoDelTest/simulation-codel-out.ipynb
. I can compare the inversion number, average throughput, and average latency between blocking and non-blocking case.