-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pseudocode for persistent congestion is too hard #4080
Conversation
This removes that function, relying instead on comments and the definition in text (which people have noted is now very clear). I have also reset a couple of extra variables in this case. It is important to catch all of these because if you don't you get poor outcomes. The only question I have is regarding bytes in flight. I think that we need to keep tracking those bytes, or the overall accounting gets messy. That is what our implementation does anyway. Closes #4010. Closes #3972.
@kazu-yamamoto : Please take a look. I'll merge this, but please respond with comments if you think something here should be changed. |
@janaiyengar This PR seems reasonable to me. I support this change. @martinthomson Thank you for brushing up the code. Since I'm a functional programmer, I prefer to use I don't understand your concern about "bytes in flight". |
Thanks @kazu-yamamoto, I share your preference for doing something like |
This removes that function, relying instead on comments and the
definition in text (which people have noted is now very clear).
I have also reset a couple of extra variables in this case. It is
important to catch all of these because if you don't you get poor
outcomes.
The only question I have is regarding bytes in flight. I think that we
need to keep tracking those bytes, or the overall accounting gets messy.
That is what our implementation does anyway.
Closes #4010.
Closes #3972.