feat(s2n-quic-dc): set max_datagram_size in ApplicationParams #2258
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
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.
Description of changes:
This change replaces the usage of
MaxMtuindc::ApplicationParamswith themax_datagram_size, which is a value based on the actual confirmed MTU size, rather than a configured setting. This removes the last remaining usage ofMaxMtufrom themtu::Controller, so I've cleaned that up a bit as well.Call-outs:
This requires setting the
InitialMtusetting to quickly probe a given MTU size, as thedc::ApplicationParamsare configured before any regular MTU probing occurs.I've also derived
CopyforApplicationParamsand added aTEST_APPLICATION_PARAMSconst for convenience.Testing:
Existing tests
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.