Update NoC link bandwidth in the MLP architecture file #2715
Conversation
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 updates the NoC link bandwidth in
mlp_benchmarks.stratixiv_arch.timing_with_a_embedded_4x4_mesh_noc_topology.xmlfrom 1e6 to 1.28e11. When VPR NoC placement was not congestion aware, this value didn't matter. With congestion-aware NoC placement, the old value causes the placement engine to focus on congestion resolution at the cost of increased aggregate bandwidth. However, 1 Mbps is unrealistly low for NoC link bandwith. Assuming that NoC links are 128-bit wide and clocked at 1 GHz, a link bandwith of 128 Gbps seems more reasonable.The results published in the FPL paper on congestion-aware NoC optimizations used 128 Gbps for NoC bandwidth.