gk: drop packets of flows not backed by a flow entry#670
Merged
AltraMayor merged 1 commit intov1.2.0-devfrom Jan 26, 2024
Merged
gk: drop packets of flows not backed by a flow entry#670AltraMayor merged 1 commit intov1.2.0-devfrom
AltraMayor merged 1 commit intov1.2.0-devfrom
Conversation
When a flow table is full, sending packets of flows not backed by
a flow entry to a Grantor server is counterproductive because
1. it stresses the request channel; and
2. it often wastes the policy decisions that cannot be installed
to the flow table since the table is full.
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
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.
When a flow table is full, sending packets of flows not backed by a flow entry to a Grantor server is counterproductive because