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

[Dynamic buffer] [Mellanox] Calculate the peer response time according to the speed #1930

Merged
merged 2 commits into from
Nov 15, 2021

Conversation

keboliu
Copy link
Collaborator

@keboliu keboliu commented Sep 24, 2021

Signed-off-by: Kebo Liu kebol@nvidia.com

What I did

Peer response time was deduced from a fixed value for all the ports speed. According to IEEE802.3 31B.3.7 at different operating speeds, the peer response time is also different, to have a more accurate headroom allocation, the way to calculate the peer response time shall be changed accordingly. See HLD update PR sonic-net/SONiC#870 for more info

Why I did it

To have the peer response time more accurate, calculate according to the definition in IEEE802.3 31B.3.7

How I verified it

Run buffer regression tests on various Mellanox platforms at various port speeds, cable lengths, with or w/o gearbox.

Details if related

Signed-off-by: Kebo Liu <kebol@nvidia.com>
@liat-grozovik
Copy link
Collaborator

@neethajohn kindly reminder. can you please review?

@liat-grozovik
Copy link
Collaborator

@neethajohn kindly reminder. this part should go to 202111 and we need to close it soon.

@keboliu keboliu changed the title [Dynamic buffer] [Mellanox] Calculate the peer response time according to the operating speed [Dynamic buffer] [Mellanox] Calculate the peer response time according to the speed Nov 12, 2021
@liat-grozovik liat-grozovik merged commit f9462c4 into sonic-net:master Nov 15, 2021
@keboliu keboliu deleted the peer-response-per-speed branch February 16, 2022 08:58
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.

4 participants