Feature/ PFCWD Hardware Recovery HLD by pinky-nexthop · Pull Request #2159 · sonic-net/SONiC

pinky-nexthop · 2025-12-16T04:23:56Z

Summary

This PR introduces a comprehensive High Level Design document for PFC Watchdog Hardware Recovery feature that provides better accuracy in storm detection and restoration compared to software-based approaches.

Key Features

Hardware-based PFC recovery mechanism using SAI attributes with improved accuracy and reduced latency
Architecture refactoring with new PfcWdHwOrch orchestrator for clean separation of hardware/software logic
New CLI command: show pfcwd status with hardware-specific information including actual timer values and granularity
Flow diagrams illustrating hardware vs software recovery decision flows and detailed workflows
Comprehensive comparison between software and hardware recovery mechanisms

Hardware Recovery Advantages

Better accuracy in storm detection: Hardware operates at line rate without software polling delays
Better accuracy in storm restoration: More precise timing without dependency on software polling intervals
Reduced latency: Immediate hardware detection and recovery actions
Lower CPU overhead: Eliminates continuous software polling, reducing system load

Document Structure

Complete SONiC HLD format following established conventions
Placed in doc/pfcwd/ directory.
References existing PFC Watchdog Design and Test Plan documents
Includes SAI API specifications and comprehensive testing requirements

Technical Highlights

Hardware timer granularity constraints and actual vs configured values
Runtime platform capability detection for automatic hardware/software selection
Backward compatibility with existing software implementation
Error handling and validation for hardware constraints

Review Focus Areas

Architecture design and orchestrator refactoring approach
SAI attribute usage and hardware integration strategy
CLI design and user experience for hardware-specific information
Testing strategy and validation approach for accuracy improvements

Related Pull Requests

Index	Description	PR Number	Pre-requisites
1	Add PFC Watchdog hardware state table definition	sonic-swss-common#1169	None
2	Update th5 parameter to support hw pfcwd	sonic-buildimage#26471	None
3	New cli "show pfcwd status" support	sonic-utilities#4384	None
4	CLI UT for PFCWD status CLI	sonic-utilities#4408	3
5	Refactor PFCWD	sonic-swss#4358	None
6	Skeleton for PFCWD Hw Recovery	sonic-swss#4403	1, 5
7	Implementation for Hw based PFCWD	sonic-swss#4412	1, 5, 6
8	UT for flexcounters and orchagent changes	sonic-swss#4418	1, 5, 6, 7
9	Add hardware-aware PFC watchdog test support	sonic-mgmt#23430	None

mssonicbld · 2025-12-16T04:24:03Z

/azp run

azure-pipelines · 2025-12-16T04:24:10Z

No pipelines are associated with this pull request.

mssonicbld · 2025-12-16T04:26:08Z

/azp run

azure-pipelines · 2025-12-16T04:26:14Z

No pipelines are associated with this pull request.

mssonicbld · 2025-12-16T04:31:10Z

/azp run

azure-pipelines · 2025-12-16T04:31:16Z

No pipelines are associated with this pull request.

mssonicbld · 2025-12-16T04:34:22Z

/azp run

azure-pipelines · 2025-12-16T04:34:28Z

No pipelines are associated with this pull request.

mssonicbld · 2025-12-16T08:43:57Z

/azp run

azure-pipelines · 2025-12-16T08:44:03Z

No pipelines are associated with this pull request.

- Comprehensive design document for hardware-based PFC recovery - Includes architecture refactoring proposal with PfcWdHwOrch - New CLI command: show pfcwd status with hardware-specific information - SAI attributes and implementation details for hardware recovery - Flow diagrams for hardware vs software recovery decision and workflow - Testing requirements and validation approach - Hardware timer granularity constraints and actual vs configured values - Comparison table highlighting differences between software and hardware recovery Signed-off-by: Pinky Agrawal <pinky@nexthop.ai>

- Changed 'CLI/YANG' to 'CLI-YANG' to fix markdown anchor link - Forward slash in header was breaking clickable navigation Signed-off-by: Pinky Agrawal <pinky@nexthop.ai>

- Updated TOC to reflect actual document structure - Removed non-existent subsections 12.2, 12.3, 12.4 - Only section 12.1 exists in the streamlined testing section Signed-off-by: Pinky Agrawal <pinky@nexthop.ai>

- Better accuracy in storm detection and restoration timing - Reduced latency compared to software polling-based approach - Lower CPU overhead by eliminating continuous software polling - Hardware operates at line rate without software delays Signed-off-by: Pinky Agrawal <pinky@nexthop.ai>

- Section 13 Open Points does not exist in the document - Cleaned up Table of Contents to match actual document structure Signed-off-by: Pinky Agrawal <pinky@nexthop.ai>

- Added CLI Data Flow subsection to TOC for proper navigation - Fixes parsing/navigation issue in section 5 Signed-off-by: Pinky Agrawal <pinky@nexthop.ai>

- Simplified the display table description in mermaid flowchart - Removed pipe characters that could cause parsing issues - Improved readability of the CLI data flow diagram Signed-off-by: Pinky Agrawal <pinky@nexthop.ai>

- Created doc/pfcwd/ directory for PFC Watchdog documentation - Moved pfc_hardware_recovery_hld.md from doc/qos/ to doc/pfcwd/ - Better organization following SONiC documentation structure - Dedicated directory allows for future PFC Watchdog related documents Signed-off-by: Pinky Agrawal <pinky@nexthop.ai>

mssonicbld · 2025-12-16T11:41:31Z

/azp run

azure-pipelines · 2025-12-16T11:41:37Z

No pipelines are associated with this pull request.

- Added STATUS column to show pfcwd status command output to indicate success/failed programming status - Updated CLI data flow diagram to include status validation - Added example showing failed configuration due to unsupported timer ranges - Updated hardware recovery workflow diagram to show event notification happening immediately after storm detection - Added conditional logic for app_managed_recovery flag: - If true: wait for SAI_QUEUE_ATTR_PFC_DLR_INIT programming - If false: hardware automatically applies recovery action Signed-off-by: Pinky Agrawal <pinky@nexthop.ai>

mssonicbld · 2025-12-18T08:39:15Z

/azp run

azure-pipelines · 2025-12-18T08:39:21Z

No pipelines are associated with this pull request.

kperumalbfn · 2026-01-21T19:10:50Z

+No YANG model changes are required for this feature. The new `show pfcwd status` command displays operational state data, not configuration data.
+
+**Rationale**: The new command displays runtime operational data (actual hardware values, granularity constraints, recovery type) rather than user configuration. This operational data is derived from:
+- Platform hardware capabilities (granularity values)


Any SAI capability query to get the hardware granularity? If so, please include SAI attributes

Added the relevant attributes to the section

linux-foundation-easycla · 2026-06-10T08:50:10Z

✅ login: pinky-nexthop / name: Pinky Agrawal (013b692, 5664c29, 6a99d4b, 7dca809, acd91cc, b88c152, cac6688, d72c840, daf7336, dcebc31, ecc08ea, eda117f, ee7c047, f203dce, fcf84a6)
❌ The email address for the commit (7dca809) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

One or more co-authors of this pull request were not found. You must specify co-authors in commit message trailer via:

Co-authored-by: name <email>

Supported Co-authored-by: formats include:

Anything <id+login@users.noreply.github.com> - it will locate your GitHub user by id part.
Anything <login@users.noreply.github.com> - it will locate your GitHub user by login part.
Anything <public-email> - it will locate your GitHub user by public-email part. Note that this email must be made public on Github.
Anything <other-email> - it will locate your GitHub user by other-email part but only if that email was used before for any other CLA as a main commit author.
login <any-valid-email> - it will locate your GitHub user by login part, note that login part must be at least 3 characters long.

Alternatively, if the co-author should not be included, remove the Co-authored-by: line from the commit message.

Please update your commit message(s) by doing git commit --amend and then git push [--force] and then request re-running CLA check via commenting on this pull request:

/easycla

linux-foundation-easycla · 2026-06-10T08:50:16Z

✅ login: pinky-nexthop / name: Pinky Agrawal (013b692, 5664c29, 6a99d4b, 7dca809, acd91cc, b88c152, cac6688, d72c840, daf7336, dcebc31, ecc08ea, eda117f, ee7c047, f203dce, fcf84a6)
❌ The email address for the commit (7dca809) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

One or more co-authors of this pull request were not found. You must specify co-authors in commit message trailer via:

Co-authored-by: name <email>

Supported Co-authored-by: formats include:

Anything <id+login@users.noreply.github.com> - it will locate your GitHub user by id part.
Anything <login@users.noreply.github.com> - it will locate your GitHub user by login part.
Anything <public-email> - it will locate your GitHub user by public-email part. Note that this email must be made public on Github.
Anything <other-email> - it will locate your GitHub user by other-email part but only if that email was used before for any other CLA as a main commit author.
login <any-valid-email> - it will locate your GitHub user by login part, note that login part must be at least 3 characters long.

Alternatively, if the co-author should not be included, remove the Co-authored-by: line from the commit message.

Please update your commit message(s) by doing git commit --amend and then git push [--force] and then request re-running CLA check via commenting on this pull request:

/easycla

linux-foundation-easycla · 2026-06-10T08:50:22Z

✅ login: pinky-nexthop / name: Pinky Agrawal (013b692, 5664c29, 6a99d4b, 7dca809, acd91cc, b88c152, cac6688, d72c840, daf7336, dcebc31, ecc08ea, eda117f, ee7c047, f203dce, fcf84a6)
❌ The email address for the commit (7dca809) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

One or more co-authors of this pull request were not found. You must specify co-authors in commit message trailer via:

Co-authored-by: name <email>

Supported Co-authored-by: formats include:

Anything <id+login@users.noreply.github.com> - it will locate your GitHub user by id part.
Anything <login@users.noreply.github.com> - it will locate your GitHub user by login part.
Anything <public-email> - it will locate your GitHub user by public-email part. Note that this email must be made public on Github.
Anything <other-email> - it will locate your GitHub user by other-email part but only if that email was used before for any other CLA as a main commit author.
login <any-valid-email> - it will locate your GitHub user by login part, note that login part must be at least 3 characters long.

Alternatively, if the co-author should not be included, remove the Co-authored-by: line from the commit message.

Please update your commit message(s) by doing git commit --amend and then git push [--force] and then request re-running CLA check via commenting on this pull request:

/easycla

linux-foundation-easycla · 2026-06-10T08:50:29Z

✅ login: pinky-nexthop / name: Pinky Agrawal (013b692, 5664c29, 6a99d4b, 7dca809, acd91cc, b88c152, cac6688, d72c840, daf7336, dcebc31, ecc08ea, eda117f, ee7c047, f203dce, fcf84a6)
❌ The email address for the commit (7dca809) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

One or more co-authors of this pull request were not found. You must specify co-authors in commit message trailer via:

Co-authored-by: name <email>

Supported Co-authored-by: formats include:

Anything <id+login@users.noreply.github.com> - it will locate your GitHub user by id part.
Anything <login@users.noreply.github.com> - it will locate your GitHub user by login part.
Anything <public-email> - it will locate your GitHub user by public-email part. Note that this email must be made public on Github.
Anything <other-email> - it will locate your GitHub user by other-email part but only if that email was used before for any other CLA as a main commit author.
login <any-valid-email> - it will locate your GitHub user by login part, note that login part must be at least 3 characters long.

Alternatively, if the co-author should not be included, remove the Co-authored-by: line from the commit message.

Please update your commit message(s) by doing git commit --amend and then git push [--force] and then request re-running CLA check via commenting on this pull request:

/easycla

linux-foundation-easycla · 2026-06-10T08:50:35Z

✅ login: pinky-nexthop / name: Pinky Agrawal (013b692, 5664c29, 6a99d4b, 7dca809, acd91cc, b88c152, cac6688, d72c840, daf7336, dcebc31, ecc08ea, eda117f, ee7c047, f203dce, fcf84a6)
❌ The email address for the commit (7dca809) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

One or more co-authors of this pull request were not found. You must specify co-authors in commit message trailer via:

Co-authored-by: name <email>

Supported Co-authored-by: formats include:

Anything <id+login@users.noreply.github.com> - it will locate your GitHub user by id part.
Anything <login@users.noreply.github.com> - it will locate your GitHub user by login part.
Anything <public-email> - it will locate your GitHub user by public-email part. Note that this email must be made public on Github.
Anything <other-email> - it will locate your GitHub user by other-email part but only if that email was used before for any other CLA as a main commit author.
login <any-valid-email> - it will locate your GitHub user by login part, note that login part must be at least 3 characters long.

Alternatively, if the co-author should not be included, remove the Co-authored-by: line from the commit message.

Please update your commit message(s) by doing git commit --amend and then git push [--force] and then request re-running CLA check via commenting on this pull request:

/easycla

linux-foundation-easycla · 2026-06-10T08:50:42Z

✅ login: pinky-nexthop / name: Pinky Agrawal (013b692, 5664c29, 6a99d4b, 7dca809, acd91cc, b88c152, cac6688, d72c840, daf7336, dcebc31, ecc08ea, eda117f, ee7c047, f203dce, fcf84a6)
❌ The email address for the commit (7dca809) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

One or more co-authors of this pull request were not found. You must specify co-authors in commit message trailer via:

Co-authored-by: name <email>

Supported Co-authored-by: formats include:

Anything <id+login@users.noreply.github.com> - it will locate your GitHub user by id part.
Anything <login@users.noreply.github.com> - it will locate your GitHub user by login part.
Anything <public-email> - it will locate your GitHub user by public-email part. Note that this email must be made public on Github.
Anything <other-email> - it will locate your GitHub user by other-email part but only if that email was used before for any other CLA as a main commit author.
login <any-valid-email> - it will locate your GitHub user by login part, note that login part must be at least 3 characters long.

Alternatively, if the co-author should not be included, remove the Co-authored-by: line from the commit message.

Please update your commit message(s) by doing git commit --amend and then git push [--force] and then request re-running CLA check via commenting on this pull request:

/easycla

linux-foundation-easycla · 2026-06-10T08:50:47Z

✅ login: pinky-nexthop / name: Pinky Agrawal (013b692, 5664c29, 6a99d4b, 7dca809, acd91cc, b88c152, cac6688, d72c840, daf7336, dcebc31, ecc08ea, eda117f, ee7c047, f203dce, fcf84a6)
❌ The email address for the commit (7dca809) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

One or more co-authors of this pull request were not found. You must specify co-authors in commit message trailer via:

Co-authored-by: name <email>

Supported Co-authored-by: formats include:

Anything <id+login@users.noreply.github.com> - it will locate your GitHub user by id part.
Anything <login@users.noreply.github.com> - it will locate your GitHub user by login part.
Anything <public-email> - it will locate your GitHub user by public-email part. Note that this email must be made public on Github.
Anything <other-email> - it will locate your GitHub user by other-email part but only if that email was used before for any other CLA as a main commit author.
login <any-valid-email> - it will locate your GitHub user by login part, note that login part must be at least 3 characters long.

Alternatively, if the co-author should not be included, remove the Co-authored-by: line from the commit message.

Please update your commit message(s) by doing git commit --amend and then git push [--force] and then request re-running CLA check via commenting on this pull request:

/easycla

linux-foundation-easycla · 2026-06-10T08:50:52Z

✅ login: pinky-nexthop / name: Pinky Agrawal (013b692, 5664c29, 6a99d4b, 7dca809, acd91cc, b88c152, cac6688, d72c840, daf7336, dcebc31, ecc08ea, eda117f, ee7c047, f203dce, fcf84a6)
❌ The email address for the commit (7dca809) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

One or more co-authors of this pull request were not found. You must specify co-authors in commit message trailer via:

Co-authored-by: name <email>

Supported Co-authored-by: formats include:

Anything <id+login@users.noreply.github.com> - it will locate your GitHub user by id part.
Anything <login@users.noreply.github.com> - it will locate your GitHub user by login part.
Anything <public-email> - it will locate your GitHub user by public-email part. Note that this email must be made public on Github.
Anything <other-email> - it will locate your GitHub user by other-email part but only if that email was used before for any other CLA as a main commit author.
login <any-valid-email> - it will locate your GitHub user by login part, note that login part must be at least 3 characters long.

Alternatively, if the co-author should not be included, remove the Co-authored-by: line from the commit message.

Please update your commit message(s) by doing git commit --amend and then git push [--force] and then request re-running CLA check via commenting on this pull request:

/easycla

linux-foundation-easycla · 2026-06-10T08:51:02Z

✅ login: pinky-nexthop / name: Pinky Agrawal (013b692, 5664c29, 6a99d4b, 7dca809, acd91cc, b88c152, cac6688, d72c840, daf7336, dcebc31, ecc08ea, eda117f, ee7c047, f203dce, fcf84a6)
❌ The email address for the commit (7dca809) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

One or more co-authors of this pull request were not found. You must specify co-authors in commit message trailer via:

Co-authored-by: name <email>

Supported Co-authored-by: formats include:

Anything <id+login@users.noreply.github.com> - it will locate your GitHub user by id part.
Anything <login@users.noreply.github.com> - it will locate your GitHub user by login part.
Anything <public-email> - it will locate your GitHub user by public-email part. Note that this email must be made public on Github.
Anything <other-email> - it will locate your GitHub user by other-email part but only if that email was used before for any other CLA as a main commit author.
login <any-valid-email> - it will locate your GitHub user by login part, note that login part must be at least 3 characters long.

Alternatively, if the co-author should not be included, remove the Co-authored-by: line from the commit message.

Please update your commit message(s) by doing git commit --amend and then git push [--force] and then request re-running CLA check via commenting on this pull request:

/easycla

linux-foundation-easycla · 2026-06-10T08:51:08Z

✅ login: pinky-nexthop / name: Pinky Agrawal (013b692, 5664c29, 6a99d4b, 7dca809, acd91cc, b88c152, cac6688, d72c840, daf7336, dcebc31, ecc08ea, eda117f, ee7c047, f203dce, fcf84a6)
❌ The email address for the commit (7dca809) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

One or more co-authors of this pull request were not found. You must specify co-authors in commit message trailer via:

Co-authored-by: name <email>

Supported Co-authored-by: formats include:

Anything <id+login@users.noreply.github.com> - it will locate your GitHub user by id part.
Anything <login@users.noreply.github.com> - it will locate your GitHub user by login part.
Anything <public-email> - it will locate your GitHub user by public-email part. Note that this email must be made public on Github.
Anything <other-email> - it will locate your GitHub user by other-email part but only if that email was used before for any other CLA as a main commit author.
login <any-valid-email> - it will locate your GitHub user by login part, note that login part must be at least 3 characters long.

Alternatively, if the co-author should not be included, remove the Co-authored-by: line from the commit message.

Please update your commit message(s) by doing git commit --amend and then git push [--force] and then request re-running CLA check via commenting on this pull request:

/easycla

mssonicbld · 2026-06-10T08:51:15Z

/azp run

azure-pipelines · 2026-06-10T08:51:22Z

No pipelines are associated with this pull request.

@eddyk-nvidia

Drive the PfcWdHwOrch-vs-PfcWdSwOrch path selection solely from the SAI capability query. Remove the SKU-based path determination and the operator override for path selection, so bringing a platform onto hardware recovery is purely a function of its SAI advertising the capability. Addresses review feedback from @eddyk-nvidia, @kperumalbfn, @yunang-c. Signed-off-by: pinky-nexthop <pinky@nexthop.ai>

mssonicbld · 2026-06-10T08:56:50Z

/azp run

azure-pipelines · 2026-06-10T08:56:56Z

No pipelines are associated with this pull request.

vmittal-msft · 2026-06-10T18:45:04Z

@saksarav-nokia @ysmanman @arista-nwolfe please help review soon as we are planning to enable HW based PFCWD for upcoming SKUs and potentially for chassis as well.

vmittal-msft · 2026-06-10T18:45:52Z

/easycla

pinky-nexthop · 2026-06-23T04:23:34Z

@prsunny @vmittal-msft
Could you please help merge this to master?

vmittal-msft · 2026-06-23T22:23:22Z

@pinky-nexthop i am waiting for @kperumalbfn to approve as well.

mssonicbld · 2026-06-24T21:06:25Z

/azp run

azure-pipelines · 2026-06-24T21:06:31Z

No pipelines are associated with this pull request.

vmittal-msft · 2026-07-01T17:43:11Z

@kperumalbfn @eddyk-nvidia please help approve.

pinky-nexthop added 8 commits December 16, 2025 11:39

Fix section 9 anchor link in Table of Contents

daf7336

- Changed 'CLI/YANG' to 'CLI-YANG' to fix markdown anchor link - Forward slash in header was breaking clickable navigation Signed-off-by: Pinky Agrawal <pinky@nexthop.ai>

Fix section 12 Table of Contents entries

fcf84a6

- Updated TOC to reflect actual document structure - Removed non-existent subsections 12.2, 12.3, 12.4 - Only section 12.1 exists in the streamlined testing section Signed-off-by: Pinky Agrawal <pinky@nexthop.ai>

Remove non-existent Open Points section from TOC

5664c29

- Section 13 Open Points does not exist in the document - Cleaned up Table of Contents to match actual document structure Signed-off-by: Pinky Agrawal <pinky@nexthop.ai>

Add missing section 5.1 to Table of Contents

cac6688

- Added CLI Data Flow subsection to TOC for proper navigation - Fixes parsing/navigation issue in section 5 Signed-off-by: Pinky Agrawal <pinky@nexthop.ai>

Fix mermaid diagram parsing in section 5.1

acd91cc

- Simplified the display table description in mermaid flowchart - Removed pipe characters that could cause parsing issues - Improved readability of the CLI data flow diagram Signed-off-by: Pinky Agrawal <pinky@nexthop.ai>

pinky-nexthop force-pushed the feature/pfc-hardware-recovery-hld branch from d793e08 to ee7c047 Compare December 16, 2025 11:41

prsunny requested review from kperumalbfn and mramezani95 December 18, 2025 00:14

vmittal-msft requested review from bingwang-ms and vmittal-msft January 5, 2026 22:43

pinky-nexthop changed the title ~~Feature/pfc hardware recovery hld~~ Feature/ PFCWD Hardware Recovery HLD Jan 13, 2026

kperumalbfn reviewed Jan 22, 2026

View reviewed changes

pinky-nexthop force-pushed the feature/pfc-hardware-recovery-hld branch from 7dca809 to cda7331 Compare June 10, 2026 08:51

pinky-nexthop force-pushed the feature/pfc-hardware-recovery-hld branch from cda7331 to 2ebf808 Compare June 10, 2026 08:56

vmittal-msft approved these changes Jun 10, 2026

View reviewed changes

saksarav-nokia approved these changes Jun 10, 2026

View reviewed changes

abhishek-nexthop mentioned this pull request Jun 23, 2026

[Hw PFCWD feature] Skeleton hw pfcwd sonic-net/sonic-swss#4403

Open

vmittal-msft closed this Jun 23, 2026

github-project-automation Bot moved this from In Progress to Done in SONiC 202605 Release Jun 23, 2026

vmittal-msft reopened this Jun 24, 2026

Uh oh!

Conversation

pinky-nexthop commented Dec 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Key Features

Hardware Recovery Advantages

Document Structure

Technical Highlights

Review Focus Areas

Related Pull Requests

Uh oh!

mssonicbld commented Dec 16, 2025

Uh oh!

azure-pipelines Bot commented Dec 16, 2025

Uh oh!

mssonicbld commented Dec 16, 2025

Uh oh!

azure-pipelines Bot commented Dec 16, 2025

Uh oh!

mssonicbld commented Dec 16, 2025

Uh oh!

azure-pipelines Bot commented Dec 16, 2025

Uh oh!

mssonicbld commented Dec 16, 2025

Uh oh!

azure-pipelines Bot commented Dec 16, 2025

Uh oh!

mssonicbld commented Dec 16, 2025

Uh oh!

azure-pipelines Bot commented Dec 16, 2025

Uh oh!

mssonicbld commented Dec 16, 2025

Uh oh!

azure-pipelines Bot commented Dec 16, 2025

Uh oh!

mssonicbld commented Dec 18, 2025

Uh oh!

azure-pipelines Bot commented Dec 18, 2025

Uh oh!

Uh oh!

Uh oh!

kperumalbfn Jan 21, 2026

Choose a reason for hiding this comment

Uh oh!

pinky-nexthop Jan 25, 2026

Choose a reason for hiding this comment

Uh oh!

linux-foundation-easycla Bot commented Jun 10, 2026

Uh oh!

linux-foundation-easycla Bot commented Jun 10, 2026

Uh oh!

linux-foundation-easycla Bot commented Jun 10, 2026

Uh oh!

linux-foundation-easycla Bot commented Jun 10, 2026

Uh oh!

linux-foundation-easycla Bot commented Jun 10, 2026

Uh oh!

linux-foundation-easycla Bot commented Jun 10, 2026

Uh oh!

linux-foundation-easycla Bot commented Jun 10, 2026

Uh oh!

linux-foundation-easycla Bot commented Jun 10, 2026

Uh oh!

linux-foundation-easycla Bot commented Jun 10, 2026

Uh oh!

linux-foundation-easycla Bot commented Jun 10, 2026

Uh oh!

mssonicbld commented Jun 10, 2026

Uh oh!

azure-pipelines Bot commented Jun 10, 2026

Uh oh!

mssonicbld commented Jun 10, 2026

Uh oh!

azure-pipelines Bot commented Jun 10, 2026

Uh oh!

vmittal-msft commented Jun 10, 2026

Uh oh!

vmittal-msft commented Jun 10, 2026

Uh oh!

pinky-nexthop commented Dec 16, 2025 •

edited

Loading