-
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
Port configuration incremental update support #2192
Port configuration incremental update support #2192
Conversation
/azpw run Azure.sonic-swss |
/AzurePipelines run Azure.sonic-swss |
Azure Pipelines successfully started running 1 pipeline(s). |
Could you please provide HLD or any issue submitted for this PR? |
/azpw run Azure.sonic-swss |
/AzurePipelines run Azure.sonic-swss |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run Azure.sonic-swss |
/AzurePipelines run Azure.sonic-swss |
Azure Pipelines successfully started running 1 pipeline(s). |
@prsunny the design was done over emails. We can share the detailed in the PR or sent it over google group. I don't think any change in the current design goes with an HLD. What do you say? |
Wait for #2195 to fix the DPB vs test failure. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-swss |
Commenter does not have sufficient privileges for PR 2192 in repo Azure/sonic-swss |
6cb59fe
to
0273978
Compare
@Junchao-Mellanox are these changes in this context ? |
Yes |
/azp run Azure.sonic-swss |
Commenter does not have sufficient privileges for PR 2192 in repo Azure/sonic-swss |
/azpw run Azure.sonic-swss |
/azpw run Azure.sonic-swss |
/AzurePipelines run Azure.sonic-swss |
Azure Pipelines successfully started running 1 pipeline(s). |
@qiluo-msft could you review? |
IMO, this is a critical change and may have wider implications. IIRC, there are legacy reasons why portsyncd is listening to CONFIG_DB table. For e.g, some implementations configure kernel MTU differently than H/W MTU. In such cases, if portsyncd is the source of truth, then H/W MTU will be same as kernel MTU. Also, I don't see the HLD reviewed/signed-off. This needs to have some thorough review. |
I am not sure if auto-neg HLD would be the right place to put this design change which is not AN specific. |
/azp run Azure.sonic-swss |
Azure Pipelines successfully started running 1 pipeline(s). |
@prgeor kindly reminder to review and signoff |
/azpw run Azure.sonic-swss |
/AzurePipelines run Azure.sonic-swss |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run Azure.sonic-swss |
/AzurePipelines run Azure.sonic-swss |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run Azure.sonic-swss |
/AzurePipelines run Azure.sonic-swss |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run Azure.sonic-swss |
/AzurePipelines run Azure.sonic-swss |
Azure Pipelines successfully started running 1 pipeline(s). |
} | ||
port_cfg_map[key] = entry; | ||
} | ||
handlePortConfig(p, port_cfg_map); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
put a log here to prove that: one field change will trigger all port configuration change
Discussion notes:
|
Close this. Will create new PR. |
HLD: sonic-net/SONiC#985
What I did
Why I did it
How I verified it
Details if related