hw: Allow collectives with NoLoopback - #239
Merged
Merged
Conversation
The datapath already handles multicast with loopback disabled: the own-input crosspoint is tied off and `expected_handshakes` excludes the own-input route. Drop the SupportLoopback assertion so that routers whose endpoint never initiates collectives can disable loopback, and document the semantics in the NoLoopback parameter. Also fix a few typos in comments. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Lore0599
approved these changes
Oct 1, 2026
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.
This PR does two things:
Routers whose endpoint never initiates collectives can now set
NoLoopback=1. WithNoLoopback=1, a collective copy addressed to the flit's own input port is dropped; this is documented in the parameter doc.Also fixes typos in comments.
🤖 Generated with Claude Code