Worked example

Worked Example for Ordering & Outstanding Rules focuses on reorder violation count, outstanding depth, completion latency spread. The goal is to connect the observable symptom to protocol mechanism, ownership, and regression risk.

A product workload shows reorder violation count, outstanding depth, completion latency spread. The first review mistake is to blame the whole interface. A better review starts by pinning one transaction, proving where protocol progress stopped, and checking whether the observed behavior is legal for Ordering & Outstanding Rules.

Sequence under inspection

SEQUENCE — Ordering & Outstanding Rules

  initiator            interconnect/PHY            target
      |  request (id) ------->  |                     |
      |                         |  forward ----------> |
      |                         |                     | work
      |                         |  <---- response ---- |
      |  <----- complete ------ |                     |
      |
   metric captured here: reorder violation count, outstanding depth, completion latency spread

Outstanding transactions timeline

OUTSTANDING = issued but not yet completed

issue   R1  R2  R3  R4
        |   |   |   |
time ---+---+---+---+----------------------->
resp            R1      R3  R2      R4
                ^^^^^^^^^^^^^^^^^^^^^^
   responses may return OUT OF ORDER across different IDs

Same ID  -> ordered
Diff ID  -> may reorder
Depth    -> how many can be in flight at once

1. Capture the failing waveform and transaction log.

2. Tag the request ID, address, endpoint, or lane.

3. Find the first response, retry, stall, or missing completion.

4. Compare against ID scoreboard, ordering matrix, litmus-style protocol sequence.

5. Choose one reversible fix and write the regression list before editing RTL or firmware.

Did the fix work?

BEFORE / AFTER — Ordering & Outstanding Rules

           failing        target
metric  |    ●              ┄┄┄┄┄┄┄
        |     \
        |      \___ ● bounded fix
        |           \
        |            ● validated
        +-------------------------------> change set
Prove the mechanism moved the metric; one good dot is not proof.

Protocol deep dive

Before naming AXI or PCIe, engineers must master layering, handshakes, ordering, and bandwidth math. These four ideas explain 80% of integration bugs.

Concept diagram

FUNDAMENTALS STACK

software intent
     |
transaction (ID, addr, len, attr, order)
     |
link/channel (handshake, credit, retry)
     |
physical (clock, reset, lanes, PHY)

Debug golden rule: never change layers without carrying transaction identity.

Metric graph

STALL BREAKDOWN EXAMPLE

ready stalls      ████████████████  42%
credit wait       ██████████        26%
ordering block    ██████            16%
reset/config      ████              10%
other             ██                6%

If ready stalls dominate, widening the bus will not help.

Metrics and artifacts to collect

• transaction latency by class

• ready stall cycles

• outstanding depth utilization

• payload efficiency vs headline width

• retry and error rate

Mini case study

A team widened a 64-bit interface to 128-bit but throughput rose only 8% because ready stalls from a slow slave dominated. Fixing slave acceptance and FIFO depth moved the metric; width did not.

Debug branches

• If latency spikes but bandwidth flat, check outstanding limits and ordering.

• If throughput collapses at high load, draw the knee curve — you are past queue stability.

• If intermittent, compare reset release order and clock domain boundaries.

Senior review question

Ask: what is the first transaction that deviates, and which spec rule does it test?

Key takeaways

• Connect every protocol claim to a transaction identity and measurable metric.

• Store the artifact (waveform, log, counter) next to every signoff decision.

Common pitfalls

• Debugging timeouts without finding the first bad transaction.

• Quoting peak bus width without payload efficiency and retry overhead.

• Treating VIP compliance as a substitute for system integration replay.

Narrative walkthrough

A team sees reorder violation count, outstanding depth, completion latency spread drop 40% after a seemingly small change near Ordering & Outstanding Rules.

They almost widen the interface. Instead they capture id=7 read burst and find W beats never matched AW len.