-
Notifications
You must be signed in to change notification settings - Fork 543
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[Dynamic Buffer Calc] Enhance the logic to check maximum headroom exc…
…eeding to cover corner scenarios (#2763) What I did Enhance the logic to check maximum headroom exceeding to cover corner scenarios Currently, the logic to check the maximum headroom exceeding works well when a user changes any buffer configuration in the dynamic buffer model, preventing all problematic configurations from being applied to the ASIC. However, it can fail when a problematic configuration is config_db.json and config reload is executed. To cover this scenario, the following actions need to be done: Take the pending PG keys and buffer profiles into account when calculating the maximum headroom Existing buffer PGs and buffer profiles can be in the pending queue since there are a large number of notifications needed to be handled during system initialization, which takes time. Take the lossy PG into account when calculating the maximum headroom. Non-default lossy PG can be added by the user in config_db.json Pass the PG to the Lua plugin when refreshing PGs for a port Signed-off-by: Stephen Sun stephens@nvidia.com Why I did it Cover corner scenarios. How I verified it Manual test, vs test, regression test (dynamic buffer)
- Loading branch information
1 parent
67552e8
commit dbda972
Showing
3 changed files
with
119 additions
and
34 deletions.
There are no files selected for viewing
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
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
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