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.
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
fix: Avoid spurious PMTUD resets #2293
base: main
Are you sure you want to change the base?
fix: Avoid spurious PMTUD resets #2293
Changes from 3 commits
376f804
685a895
8a37331
e897be7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You mentioned that the reason for this change was that we were resetting PMTUD too often, but this will stop a probe when it looks like we should be setting it higher.
I'm not following this. The logic here is that we've detected losses, but they are on larger packets than we are currently sending. That is, we are probing and have seem to have three packet sizes, decreasing in size:
MAX_PROBES
of losses.However, the current MTU is going to be the same as this second value. That is, when we are probing, we'll have
self.mtu == largest_ok_mtu
when the probed size. The probed size is only ever one step larger than the current MTU. That means that this test will always fail.Is this extra condition is even needed? If we ever get
MAX_PROBES
losses, I can think of the following cases:largest_ok_mtu
) in which case you want to fail the probe and settle at the current MTU.I can see a case for a
>=
here, perhaps. I don't understand the guard otherwise. As it is, it looks like we'll never stop probing due to losses.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't this pure contrivance? We don't probe in this odd pattern.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this is made up to test corner cases.