Skip to content
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

Fix ndppd occupy high CPU usage problem #11036

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

kuanyu99
Copy link
Contributor

@kuanyu99 kuanyu99 commented Jun 6, 2022

Why I did it

In t1-topology, we frequently see the ndppd use a lot of CPU usage.

How I did it

Make the route-ttl setting correctly generate inside the /etc/ndppd.conf of swss container.

How to verify it

Run the test_cpu_memory_usage.py for multiple times and make sure the ndppd will not fail the test.

Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106
  • 202111

Description for the changelog

Based on the PR#7456, the route-ttl setting should not put inside the vlan interface if-else block

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

* Based on the PR#7456, the route-ttl setting should not put
  inside the vlan interface if-else blok
@kuanyu99 kuanyu99 requested a review from lguohan as a code owner June 6, 2022 02:23
@lguohan lguohan requested a review from a team June 6, 2022 05:06
@prsunny prsunny requested a review from theasianpianist June 7, 2022 17:39
@theasianpianist
Copy link
Contributor

Can we change this to not run on T1 devices altogether?

@kuanyu99
Copy link
Contributor Author

kuanyu99 commented Jun 9, 2022

Can we change this to not run on T1 devices altogether?

Do you mean if the ndppd can be an optional program when the device in a T1 topology?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants