[ppi]: Implement port bulk comparison logic#2564
[ppi]: Implement port bulk comparison logic#2564liat-grozovik merged 6 commits intosonic-net:masterfrom
Conversation
310808c to
032efa2
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run |
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run |
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run |
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
032efa2 to
d7741a0
Compare
|
@nazariig can you attach the test results to the PR? |
|
@nazariig can you provide more detailed test results. Have you tested AN/LT? FEC? |
d7741a0 to
cea1516
Compare
|
@nazariig please share the performance data for ports create as part of create_switch (SAI profile file) vs bulk ports create from portsorch for your platform |
| attrPtrList.push_back(attrDataList.back().data()); | ||
| } | ||
|
|
||
| auto status = sai_port_api->create_ports( |
There was a problem hiding this comment.
@prgeor these statements are not relevant:
- Checking for NULL doesn't make any sense - the bulk API (sairedis) is implemented and currently available for all the vendors
- The current syncd implementation doesn't propagate
SAI_STATUS_NOT_SUPPORTEDandSAI_STATUS_NOT_IMPLEMENTEDcodes to upper layer. Instead, it automatically falls back to the legacy one-by-one processing of the requested bulk operation objects. Taking this into consideration, there is no point to have a capabilities check in swss
|
@nazariig can you simulate a scenario where your changes are tested on your platform where it does not support bulk port creation? |
it is not relevant in context of this feature, since |
Signed-off-by: Nazarii Hnydyn <[email protected]>
Signed-off-by: Nazarii Hnydyn <[email protected]>
Signed-off-by: Nazarii Hnydyn <[email protected]>
Signed-off-by: Nazarii Hnydyn <[email protected]>
Signed-off-by: Nazarii Hnydyn <[email protected]>
|
/azpw run |
|
/AzurePipelines run |
|
No commit pushedDate could be found for PR 2564 in repo sonic-net/sonic-swss |
|
/azpw run Azure.sonic-swss |
|
/AzurePipelines run Azure.sonic-swss |
|
No commit pushedDate could be found for PR 2564 in repo sonic-net/sonic-swss |
|
@nazariig , could you please try the command "/azpw run Azure.sonic-swss" again? |
|
/azpw run Azure.sonic-swss |
|
/AzurePipelines run Azure.sonic-swss |
|
Azure Pipelines successfully started running 1 pipeline(s). |
- What I did Implemented port bulk add/remove comparison logic Refactored Port OA to facilitate port config operations - Why I did it To improve switch Fast Boot startup time - How I verified it UT tests VS tests Backport from master: [ppi]: Implement port bulk comparison logic #2564 Signed-off-by: Nazarii Hnydyn <[email protected]>
|
Backported PR was approved and merged. moving forward with this PR as well. |
DEPENDS: [202211][ppi]: Implement port bulk comparison logic (#2564) #2821 HLD: sonic-net/SONiC#1084 What I did Removed unused code Why I did it To complete code cleanup How I verified it UT tests VS tests Details if related Backport from master: [ppi]: General code cleanup: remove unused methods #2867
- What I did Implemented port bulk add/remove comparison logic Refactored Port OA to facilitate port config operations - Why I did it To improve switch Fast Boot startup time - How I verified it UT tests VS tests Signed-off-by: Nazarii Hnydyn <[email protected]>
- What I did Implemented port bulk add/remove comparison logic Refactored Port OA to facilitate port config operations - Why I did it To improve switch Fast Boot startup time - How I verified it UT tests VS tests Signed-off-by: Nazarii Hnydyn <[email protected]>

Signed-off-by: Nazarii Hnydyn [email protected]
DEPENDS:
HLD: sonic-net/SONiC#1084
What I did
Why I did it
How I verified it
Details if related