Skip to content

hw: Add floo cut for NW routers - #249

Draft
Lore0599 wants to merge 2 commits into
mainfrom
lleone/floo-nw-cut
Draft

Lore0599 wants to merge 2 commits into
mainfrom
lleone/floo-nw-cut

Conversation

@Lore0599

@Lore0599 Lore0599 commented Nov 4, 2026 •

Copy link
Copy Markdown
Collaborator

Add floo_nw_cut and fix floo_cut for multiple physical channels

What changed

  • floo_cut
    • Fixed for NumPhysChannels == NumVirtChannels: one spill register and data bus per virtual channel, fully parallel paths, no arbiter.
    • Kept the floo_vc_arbiter path for one shared physical channel, VcNaive only (new VcImpl parameter, default VcNaive).

⚠️ Attention ⚠️

Other VcImpl configurations have not been tested. For this reason, the floo_vc_arbiter is used in its default configuration, as in the original version of this file.

We are currently using this cut in the Gwaihir project, with two different data links in parallel. In the future, the module should be tested with the other VcImpl options recently added to FlooNoC: credit based and preemptive valid.

To track this task I opened Issue#250

floo_cut dropped all but one physical channel when NumPhysChannels > 1.
Map virtual channel v to physical channel v like floo_router does and
reject other combinations. floo_nw_cut cuts both directions of a
narrow-wide link with three floo_cut instances and has a self-checking
testbench (2 virtual and 2 physical wide channels, random backpressure).
Keep floo_cut for NumPhysChannels == NumVirtChannels, where every
virtual channel is an independent spill register path, and add back the
floo_vc_arbiter for one shared physical channel with VcNaive. Other
configurations are rejected by an assertion that documents how to
support them. Extend tb_floo_nw_cut to cover the wide link with no
decoupling, a shared physical channel and separate physical channels.

This branch has not been deployed

No deployments
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.

1 participant