[FC] Support Policer counter #3415
Draft
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
|
|
Signed-off-by: shiraez <[email protected]>
shiraez
force-pushed
the
policer_counter
branch
from
b835492 to
732dd0a
Compare
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.
What I did
Added the implantation for policer counter
Added mechanisms to collect and expose counters for various policing actions, such as packets dropped or marked.
Orchagent Updates: Enhanced Orchagent to manage the new policer counters and ensure their correct synchronization with SAI.
Unit Tests: Included unit tests to validate the correctness of the policer counter.
Why I did it
Simplifies debugging of policy enforcement issues by allowing real-time counter analysis.
How I verified it
Details if related