Skip to content

[orchagent] PFC WD support for BFN platform#916

Merged
lguohan merged 1 commit intosonic-net:201811from
vsenchyshyn:bfn-pfc-wd-support-201811
Jun 9, 2019
Merged

[orchagent] PFC WD support for BFN platform#916
lguohan merged 1 commit intosonic-net:201811from
vsenchyshyn:bfn-pfc-wd-support-201811

Conversation

@vsenchyshyn
Copy link
Copy Markdown
Contributor

What I did
This is a clone of this PR: #823 for 201811

Why I did it

How I verified it
pfc_wd community test on barefoot platform passed.

Details if related

@vsenchyshyn
Copy link
Copy Markdown
Contributor Author

@lguohan @wendani Please review.

@wendani
Copy link
Copy Markdown
Contributor

wendani commented May 30, 2019

@vsenchyshyn add a comment "retest this please" can trigger a new build and test chain. We do not need to create a new pr

@vsenchyshyn
Copy link
Copy Markdown
Contributor Author

@vsenchyshyn add a comment "retest this please" can trigger a new build and test chain. We do not need to create a new pr

Wow interesting trick! Thanks a bunch!

@wendani
Copy link
Copy Markdown
Contributor

wendani commented Jun 1, 2019

Also you do not need to create a separate pr specifically for 20181130 image. There is a label in the label section called "request in 20181130 image". Just add it to your original pr to mark the necessity for 1130 inclusive. Maintainer will pick it up later once it is merged to master

Copy link
Copy Markdown
Contributor

@stcheng stcheng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could you correct the commit title name to orchagent?

@vsenchyshyn vsenchyshyn changed the title [orcghagent] PFC WD support for BFN platform [orchagent] PFC WD support for BFN platform Jun 3, 2019
Signed-off-by: Vitaliy Senchyshyn <vsenchyshyn@barefootnetworks.com>
@vsenchyshyn vsenchyshyn force-pushed the bfn-pfc-wd-support-201811 branch from c74ae44 to e9f43a4 Compare June 3, 2019 10:16
@vsenchyshyn
Copy link
Copy Markdown
Contributor Author

could you correct the commit title name to orchagent?

Done!

@lguohan lguohan requested a review from wendani June 4, 2019 16:54
(occupancy_bytes == 0 and packets - packets_last == 0 and (pfc_duration - pfc_duration_last) > poll_time * 0.8) then
if time_left <= poll_time then
redis.call('HDEL', counters_table_name .. ':' .. port_id, pfc_rx_pkt_key .. '_last')
redis.call('HDEL', counters_table_name .. ':' .. port_id, pfc_duration_key .. '_last')
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My comments stay the same as earlier. Drop lines 74 & 75 if there is no proof that bfn has double storm signaling problem.

if is_deadlock == false then
redis.call('HSET', counters_table_name .. ':' .. port_id, pfc_rx_pkt_key .. '_last', pfc_rx_packets)
redis.call('HSET', counters_table_name .. ':' .. port_id, pfc_duration_key .. '_last', pfc_duration)
end
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Drop the 'if is_deadlock == false' condition. Lines 93 - 96

@wendani wendani self-requested a review June 5, 2019 16:29
@lguohan lguohan merged commit 93497ec into sonic-net:201811 Jun 9, 2019
EdenGri pushed a commit to EdenGri/sonic-swss that referenced this pull request Feb 28, 2022
This is to revert the change to the reboot command in 7105400.

Platform reboot is not supported by the kdump kernel, as the platform drivers are not loaded. With the existing code, there are some error messages printed, but the device is still rebooted by CPU. The change here helps to avoid the error messages.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants