Get the maximum port number from the PORT_TABLE in APPDB instead of calculating it from netdevs. - #6
Merged
chenkelly merged 1 commit intoAug 15, 2025
Conversation
…alculating it from netdevs.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What I did
Get the maximum port number from the PORT_TABLE in APPDB instead of calculating it from netdevs.
Why I did it
During a fast reboot: when stpmgrd informs stpd that ports are ready, some network devices (netdevs) may not be fully created yet. As a result, stpd calculates a lower-than-actual maximum port number, leading to insufficient memory allocation.
How I verified it
Execute 'fast-reboot' to make sure the maximum port number is correct.
Details if related
Notes
Related to edge-core/sonic-swss#142.