IP fragmentation auto-tuning #71
Merged
Conversation
This file contains hidden or 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
For IPv[46] fragmentation reassembly, memory is capped at net.ipv[46].ip[6]frag_high_thresh Fragmentation reassembly can fail if this value is set too low; monitor for fragmentation reassembly and bump value if needed. Avoid bumping it if assembly faiures constitute too high a proportion of reassembly events; this may signify a DoS. Tests verify this works in non-global/global network namespaces. To do: cap high_thresh? Signed-off-by: Alan Maguire <[email protected]>
oracle-contributor-agreement
bot
added
the
OCA Verified
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
For IPv[46] fragmentation reassembly, memory is capped at
net.ipv[46].ip[6]frag_high_thresh
Fragmentation reassembly can fail if this value is set too low; monitor for fragmentation reassembly and bump value if needed.
Avoid bumping it if assembly faiures constitute too high a proportion of reassembly events; this may signify a DoS.
Tests verify this works in non-global/global network namespaces.
To do: cap high_thresh?