DenseChip

PCIe/CXL Deep Dive · All levels

Completions, Tags, and Split-Transaction Tracking: Interview Drills

Interview Drills for Completions, Tags, and Split-Transaction Tracking.

Interview drills

Interview Drills for Completions, Tags, and Split-Transaction Tracking focuses on Outstanding tag utilization, completion timeout rate, and split completion assembly errors. The purpose is to turn memory observations into mechanism-backed actions with explicit owners and release-safe validation.

diagram
PROMPT
You observe Outstanding tag utilization, completion timeout rate, and split completion assembly errors on Completions, Tags, and Split-Transaction Tracking. Explain root cause and release decision.

STRONG ANSWER
1. Defines failing traffic context and first transition loss.
2. Explains mechanism: Non-posted requests allocate tags tracked until completions return. Split completions for large reads must assemble in order; tag leaks stall future requests and mimic performance cliffs.
3. Requests proving artifact: Tag pool timeline, completion latency histogram, and timeout register dump
4. Proposes bounded fix + owner + rollback-safe validation.

WEAK ANSWER
Gives generic PCIe tuning ideas without command evidence, owner accountability, or risk controls.

Interview evidence matrix

diagram
PCIe/CXL EVIDENCE MATRIX - Completions, Tags, and Split-Transaction Tracking

+-------------------------------+--------------------------------+--------------------------------+---------------------------+
| Evidence                      | Tells you                      | Does not prove                 | Next action               |
+-------------------------------+--------------------------------+--------------------------------+---------------------------+
| TLP type mix + credit stall counters    | protocol-layer stall cost    | link integrity and replay behavior   | inspect training margins  |
| queue age + class breakdown   | fairness and starvation risk   | command legality details       | parse command timeline    |
| LTSSM timeline + ordered set progression | timing-window pressure         | root cause by itself           | correlate with topology map|
| eye / Vref / skew snapshots   | PHY margin and drift behavior  | controller policy quality      | pair with schedule logs   |
| CE/UE + scrub telemetry       | reliability trajectory         | immediate perf bottleneck only | map to hotspot apcieesses  |
+-------------------------------+--------------------------------+--------------------------------+---------------------------+

PCIe/CXL deep dive

Transaction patterns (tags, atomics, DMA, P2P) dominate performance and correctness beyond raw link speed.

Concept diagram

diagram
TRANSACTION LIFECYCLE

MemRd -> tag alloc -> completion(s) -> tag free

Metric graph

diagram
TRANSACTION LOSS MIX

tag exhaustion      █████
P2P fallback        ████
atomic retry        ███

Reports and artifacts

  • TLP type histogram

  • tag pool timeline

  • atomic trace

  • P2P path verification matrix

Mini case study

Tag leaks after split-completion stress stalled non-posted traffic while the link remained in L0.

Debug branches

  • Track outstanding tags and completion latency

  • Verify P2P with ACS/IOMMU policy matrix

  • Run coherency litmus for atomics and ordering attrs

Senior review question

Ask: which latency, bandwidth, and reliability evidence proves this PCIe/CXL topic is closed under real traffic?

Key takeaways

  • Always tie controller and PHY counter shifts to application latency and throughput outcomes.

  • Lock firmware timing profile, thermal condition, and DIMM state before comparing PCIe/CXL captures.

Common pitfalls

  • Chasing peak bandwidth while ignoring p99 latency and fairness tails.

  • Changing timing guardbands without separating SI noise from scheduling issues.

  • Declaring closure without reliability gates, fault injection, and regression replay.

Interview answer expansion

Strong interview answers for Completions, Tags, and Split-Transaction Tracking start with workload framing and metric framing, then explain mechanism plainly: Non-posted requests allocate tags tracked until completions return. Split completions for large reads must assemble in order; tag leaks stall future requests and mimic performance cliffs.

Then propose a measurement plan: TLP routing, credit dynamics, turnaround cost, RAS interference, and PHY margin where relevant.

Finally, present one bounded fix plus regression risk. PCIe/CXL interviews reward explicit tradeoff ownership, not generic tuning slogans.

Practice this lesson