CPU Design · All levels

Multi-Issue and Port Conflicts

Execution Units & Pipelines: Superscalar throughput depends on instruction mix mapping cleanly to available ports; contention spikes when many uops require the same functional pipes in adjacent cycles.

What this topic teaches

Multi-Issue and Port Conflicts turns CPU design theory into actionable review decisions. Superscalar throughput depends on instruction mix mapping cleanly to available ports; contention spikes when many uops require the same functional pipes in adjacent cycles. The target is evidence-backed closure, not opinion-driven tuning.

Senior-engineer framing question

When issue slot utilization, execution port pressure, and structural hazard stalls shifts, can you prove first failing stage, dominant mechanism, accountable owner, and release-safe mitigation?

diagram

CPU PIPELINE VIEW - Multi-Issue and Port Conflicts

fetch -> decode -> rename -> dispatch -> execute -> retire
  |        |         |          |         |         |
icache   uop flow   map table  queueing  FU ports  ROB commit

steady-state goal:
keep every stage supplied without bubbles or flush storms

Focus: connect metric movement to the first stage loss
Metric tracked: issue slot utilization, execution port pressure, and structural hazard stalls

Architecture visuals

Draw the mechanism before changing knobs. These visuals are optimized for design reviews and interview whiteboards.

Port contention under superscalar issue

diagram

OOO CORE BLOCK DIAGRAM - Multi-Issue and Port Conflicts

decode -> rename -> dispatch -> reservation stations -> execute units
             |                        |                    |
       free-list / map table       wakeup-select         writeback
             \                        |                    /
              +-------- reorder buffer / retire ---------+

Focus: highlight multi-issue candidates colliding on shared execution ports

Port conflict root-cause tree

diagram

ROOT-CAUSE TREE - Multi-Issue and Port Conflicts

issue slot utilization, execution port pressure, and structural hazard stalls regressed
        |
  reproducible on fixed seed?
      /               \
    no                 yes
    |                   |
env/tool drift      first failing stage?
                    /        |        \
                front-end   execute   memory/system
                   |          |            |
              fetch/decode   port/ROB   cache/TLB/NoC

Stop at first confirmed mechanism, then patch with owner accountability.

Out-of-order control map

diagram

OOO CORE BLOCK DIAGRAM - Multi-Issue and Port Conflicts

decode -> rename -> dispatch -> reservation stations -> execute units
             |                        |                    |
       free-list / map table       wakeup-select         writeback
             \                        |                    /
              +-------- reorder buffer / retire ---------+

Focus: rename to retire dataflow

Memory hierarchy map

diagram

CPU CACHE + MEMORY HIERARCHY - Multi-Issue and Port Conflicts

                 [ L1I ]   [ L1D ]
               32-64KB, ~4 cycles
                      \     /
                       [  L2  ]
                 512KB-2MB, ~12 cycles
                           |
                         [ L3 ]
               shared LLC, 30-60 cycles
                           |
                    [ DDR/HBM memory ]
                    80-150ns effective

Optimization lens: latency vs capacity tradeoff

Speculation lens

diagram

BRANCH PREDICTOR VIEW - Multi-Issue and Port Conflicts

fetch PC -> BTB lookup -> direction predictor -> target select -> fetch redirect
               |               |                    |
          BTB miss cost     confidence         RAS / indirect path

branch resolves in execute:
correct prediction  -> pipeline keeps flowing
mispredict          -> flush + restart + refill

Focus: minimize wrong-path work

Ownership layers

diagram

CPU OWNERSHIP LAYERS - Multi-Issue and Port Conflicts

artifact area     owner
----------------  ----------------------------
architecture    scheduler owner
RTL/microarch   compiler backend owner
software/tools  performance lead

Rule: every regressed metric must map to an explicit owner and closure artifact.

Evidence required

Primary metric: issue slot utilization, execution port pressure, and structural hazard stalls.
Primary artifact: port pressure heatmap, instruction-port mapping table, and stall attribution snapshot.
Owners to include: scheduler owner, compiler backend owner, performance lead.
One reproducible failing workload and one stable comparator run.
One run with fully locked environment metadata for causal comparison.

Compute-memory limit lens

diagram

CPU ROOFLINE - Multi-Issue and Port Conflicts

performance
   ^
   |                 compute roof
   |                /
   |               /
   |--------------/---------------- memory roof
   +----------------------------------------------> arithmetic intensity
      memory-bound                 compute-bound

Interpretation: separate compute and memory limits

Key takeaways

Classify stage loss before proposing fixes.
Use artifacts to separate mechanism from symptoms.
Close with owner accountability and rollback criteria.

Common pitfalls

Using average IPC alone while ignoring tail behavior.
Comparing traces across mismatched binaries or thermal states.
Calling closure without workload-level validation.

CPU deep dive

Execution throughput depends on port balance, bypass quality, and realistic instruction mix assumptions.

Concept diagram

diagram

EXECUTION DATAPATH

issue -> ALU/FPU/vector/LSQ ports -> writeback -> retire

Metric graph

diagram

EXECUTION LOSS DRIVERS

port conflicts      █████
bypass hazards      ████
LSQ ordering stalls ███

Reports and artifacts

port pressure heatmap
pipeline hazard report
ALU/FPU/vector utilization split
LSQ ordering diagnostics

Mini case study

A compiler scheduling update over-concentrated uops on one port class, reducing effective multi-issue throughput.

Debug branches

Map instruction classes to port availability
Validate forwarding depth against dependency chains
Inspect LSQ ordering events before widening pipes

Senior review question

Ask: which CPI/latency evidence proves this topic is truly closed beyond synthetic benchmarks?

Key takeaways

Always connect microarchitectural counter changes to product workload outcomes.
Lock binary, compiler, firmware, and thermal metadata before comparing CPU traces.

Common pitfalls

Treating average IPC as sufficient proof while ignoring latency tails and outliers.
Applying predictor or prefetch tweaks without first-failing-stage attribution.
Declaring closure without reproducible perf, correctness, and power gates.

Practice this lesson