-
Notifications
You must be signed in to change notification settings - Fork 558
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
[portsorch]: Implement port PFC asym capability check #2942
Conversation
18f278e
to
504dc7d
Compare
/azpw run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
@prsunny / @qiluo-msft please help to review & merge |
504dc7d
to
294d87f
Compare
@prsunny / @qiluo-msft just a kind reminder |
@prsunny / @qiluo-msft just a kind reminder |
Signed-off-by: Nazarii Hnydyn <nazariig@nvidia.com>
b2a967c
to
1c8510e
Compare
Signed-off-by: Nazarii Hnydyn <nazariig@nvidia.com>
@StormLiangMS Tested on top of 202305 commit sonic-net/sonic-buildimage@40d1159 |
hi @dgsudharsan this is an enhancement, let's have it in next release. |
@StormLiangMS This is not enhancement but a bug fix. If a platform doesn’t support pfc asym, by default SONiC will crash. We added a capability to check if pfc asym is supported before programming the configuration to SAI |
* [portsorch]: Implement port PFC asym capability check.
Signed-off-by: Nazarii Hnydyn nazariig@nvidia.com
Capability check helps to avoid port misconfiguration on systems where PFC asymmetric is not supported
What I did
Why I did it
How I verified it
Details if related