When is a feedthrough better than routing around a block?
From PDVerse PnR Interview Handbook, part of the pdVerse Mentor Guide
Short Answer
The naive instinct is "shortest path wins," but a feedthrough is a system-level tradeoff, not a pure geometry problem โ the straight line through a block can beat the detour on distance while still being the wrong engineering choice. A feedthrough is worth it when the top-level distance and timing benefit it buys clearly outweighs what it costs the block it passes through โ pin budget, routing capacity, voltage-area compatibility, buffering needs, and future ECO flexibility.
Technical Explanation
- Compare the detour length honestly against the feedthrough's real benefit, not just eyeballed distance โ a detour that's only marginally longer than the feedthrough almost never justifies the pin and routing cost to the block.
- Check pin-pair alignment โ if the feedthrough's entry and exit pins line up naturally with existing block pin locations, the cost is much lower than if new pins have to be carved out specifically for this route.
- Consider whether the feedthrough can be a reusable path (multiple signals sharing the same physical corridor) rather than a one-off โ reuse dramatically improves the cost/benefit math.
- Also weigh internal congestion, hierarchy ownership (whose sign-off is needed), and any power-domain or voltage-area crossing the feedthrough would introduce โ a feedthrough that crosses domains adds isolation/level-shifting cost that a detour avoids entirely.
Formula Or Decision Rule
Decision rule: choose the alternative with lower combined system risk and an explicit block-owner agreement.
What To Check
- Warning sign: A top-level timing fix silently consumes scarce block pins or crosses an incompatible domain.
- Inspect: choose one affected region, macro, row, pin, path, or net and trace the physical cause.
- Correct: Redesign the route or feedthrough, assign ownership, and check both block and top-level consequences.
Command Checks & Actions
- check_feedthroughs -net_constraints -topo_constraints -pure -mixed: checks targeted feedthrough classes and constraints
- report_feedthroughs -reporting_style block_based: reports feedthrough nets and traversed blocks
Run only the commands needed for this question. Save the report with the floorplan version and analysis context.
Healthy, Suspicious & Hard-stop Results
- Healthy: A feedthrough is better when the top-level distance and timing benefit exceeds the blockโs pin, route, voltage-area, buffering, and ECO cost.
- Hard stop: required legality or physical feasibility is missing or unexplained.
Common Mistake
The Trap: Do not hide the symptom with an arbitrary utilisation, halo, channel, blockage, pin move, or die-size change.
What The Interviewer Is Testing
โ to measurable physical evidence and an owned correction.
Follow-up Question & Model Response
"* Candidate Model Response: Model response: โI would change it if the same controlled rerun shows that a top-level timing fix silently consumes scarce block pins or crosses an incompatible domain. โ
Physical Design & Planning Handbook
Master ASIC Physical Design Planning & Floorplanning
Dive into 14 comprehensive chapters covering netlist sanity, FinFET grids, macro placement, power grids, CTS, and timing budgeting.
Offline PDF Bundle
Want all 1109 questions offline?
Get the complete 4-book PDF bundle (PnR, STA, MMMC, Low Power) with a clickable table of contents - no ads, no internet needed.

Continue practising