-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[202012][PFCWD + Asym PFC]: Allow PFCWD to detect PFC storm on all pr… #1887
[202012][PFCWD + Asym PFC]: Allow PFCWD to detect PFC storm on all pr… #1887
Conversation
This pull request fixes 1 alert when merging 21c0f04 into 8471f42 - view on LGTM.com fixed alerts:
|
@volodymyrsamotiy can you please handle LGTM error? |
@volodymyrsamotiy please check LGTM failure and handle |
It is not related to my changes.
|
This pull request fixes 1 alert when merging 21c0f04 into 8471f42 - view on LGTM.com fixed alerts:
|
@qiluo-msft do you have an idea how to overcome it? |
@neethajohn could you please help to merge regardless of the LGM issue or you can suggest how to overcome it? |
@volodymyrsamotiy it seems lgtm is not working also on 201911. please see #1901 |
21c0f04
to
89cf1a2
Compare
This pull request fixes 1 alert when merging 89cf1a2 into 6b0b2c4 - view on LGTM.com fixed alerts:
|
…iorities when Asym PFC is enabled Signed-off-by: Volodymyr Samotiy <volodymyrs@nvidia.com>
89cf1a2
to
48973be
Compare
This pull request fixes 1 alert when merging 48973be into 6b0b2c4 - view on LGTM.com fixed alerts:
|
/azpw run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
…wd_asym_pfc_202012
This pull request fixes 1 alert when merging eedaf66 into ee9c30d - view on LGTM.com fixed alerts:
|
@neethajohn kindly reminder for the review |
Please resolve the conflicts. |
…wd_asym_pfc_202012 Conflicts: orchagent/pfcactionhandler.cpp
This pull request fixes 1 alert when merging 220cc0e into 9008a01 - view on LGTM.com fixed alerts:
|
/azp run Azure.sonic-swss |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-swss |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run LGTM |
No pipelines are associated with this pull request. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
…wd_asym_pfc_202012
This pull request fixes 1 alert when merging 5e93a16 into 0b120fa - view on LGTM.com fixed alerts:
|
…om upstream Signed-off-by: Volodymyr Samotiy <volodymyrs@nvidia.com>
This pull request fixes 1 alert when merging 57f7d79 into 0b120fa - view on LGTM.com fixed alerts:
|
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@neethajohn could you please help to review? |
…iorities when Asym PFC is enabled
Signed-off-by: Volodymyr Samotiy volodymyrs@nvidia.com
Same as #1360 but for 202012 since cherry-pick has merge conflicts
What I did
Add possibility for PFCWD to detect PFC storm on all priorities when asymmetric PFC is enabled.
According to requirements PFCWD should detect PFC storm on the lossy priorities for the port on which asymmetric PFC is enabled.
(when asymmetric PFC is enabled on some port that means such port is enabled for receiving PFC frames on all priorities)
Why I did it
To fix issue #1128.
How I verified it
pause
frames to the test port for all priorities.Details if related
N/A