[crmorch]: neighbor used counter increased twice (#472) - Cherry-pick to 201803 branch#501
Merged
prsunny merged 1 commit intosonic-net:201803from May 14, 2018
Conversation
* [crmorch]: neighbor used counter increased twice
prsunny
approved these changes
May 10, 2018
|
@prsunny pls check CLA already signed. |
prsunny
approved these changes
May 14, 2018
Janetxxx
pushed a commit
to Janetxxx/sonic-swss
that referenced
this pull request
Nov 10, 2025
…ic-net#501) * [crmorch]: neighbor used counter increased twice
jianyuewu
pushed a commit
to jianyuewu/sonic-swss
that referenced
this pull request
Dec 24, 2025
…ss-comp… (sonic-net#501) Current armhf Sonic build on amd64 host uses qemu emulation. Due to the nature of the emulation it takes a very long time, about 22-24 hours to complete the build. The change I did to improve the building time ports Sonic armhf build on amd64 host for Marvell platform for debian buster to use cross-compilation on arm64 host for armhf target. The overall Sonic armhf building time using cross-compilation is about 6 hours. The Sonic configure and build for the armhf cross-compilation is as following: NOJESSIE=1 NOSTRETCH=1 BLDENV=buster CROSS_BLDENV=1 make configure PLATFORM=marvell-armhf PLATFORM_ARCH=armhf NOJESSIE=1 NOSTRETCH=1 BLDENV=buster CROSS_BLDENV=1 make target/sonic-marvell-armhf.bin Sonic module should check if $CROSS_BUILD_ENVIRON is 'y' to make sure that it is cross-compilation build. Co-authored-by: marvell <marvell@cpss-build3.marvell.com>
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
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
Cherry-picked the #472 PR
Why I did it
The bug with duplicate neighbor count is present in 201803 branch
How I verified it
crm show resources ipv4 neighborshows 0crm show resources ipv4 neighborshows 10Details if related