This page is the "put a number on it" companion to the parent SerDes note . The parent gave you the formulas; here we hunt down every kind of question those formulas can produce and grind each one to a checkable number.
Intuition Read this first
A formula is only trustworthy once you have watched it survive the nasty inputs: the slow bus, the impossibly fast bus, the zero-skew ideal, the encoding that eats your bandwidth, the crystal that drifts. Below we build a matrix of every scenario class, then solve one example per cell. If you ever meet a SerDes number problem in an exam, it lives in one of these boxes.
Every SerDes numeric question is really one of these situations. The columns are the quantity you solve for ; the rows are the regime (which physical effect dominates or degenerates).
Regime → \ Solves for →
Skew / parallel limit
Serial data rate
Timing / CDR margin
Low speed (skew tiny)
Ex 1
—
—
High speed (skew fatal)
Ex 2
—
—
Degenerate / ideal (zero input)
Ex 3 (zero skew)
—
Ex 7 (zero drift)
Encoding overhead
—
Ex 4 (8b/10b), Ex 5 (128b/130b)
—
Multi-lane scaling
—
Ex 6 (x16)
—
Bit-period / sampling
—
—
Ex 8 (CDR budget)
Real-world word problem
Ex 9 (cable choice)
Ex 9
Ex 9
Exam twist (limiting value)
Ex 10 (crossover speed)
Ex 10
Ex 10
The two constants we reuse everywhere:
Here is the same map as a picture — which example sits in which regime:
Worked example A gentle 100 MHz parallel bus
A 32-bit parallel bus runs at 100 MHz . Worst-case trace-length mismatch between the shortest and longest data trace is 8 mm . What fraction of the clock period is lost to skew? Is the bus safe?
Forecast: guess now — is the skew under 1% of the period, or over 10%? (At only 100 MHz the period is long, so bet on "tiny".)
Convert length mismatch to time (skew).
Δ t s k e w = v l = 1.8 × 1 0 8 8 × 1 0 − 3 = 4.44 × 1 0 − 11 s = 44.4 ps
Why this step? Skew is only a delay difference; the extra 8 mm of copper is what makes one bit arrive late. Delay = distance ÷ speed.
Find the clock period.
T c l k = 100 × 1 0 6 1 = 10 ns = 10000 ps
Why this step? We judge skew relative to how long a bit is allowed to settle — the period.
Compute skew as a fraction.
10000 44.4 = 0.00444 = 0.44%
Why this step? A percentage is the only honest measure: 44 ps is meaningless until compared to the period.
Verify: 0.44% ≪ typical 15% danger threshold → safe . Units: ps/ps is dimensionless, correct. Sanity: slow clock ⇒ skew negligible, matches the parent's "at 1 GHz it's still fine" claim.
Worked example The same wires at 6 GHz
Keep the 8 mm mismatch (skew = 44.4 ps from Ex 1). Now push the parallel clock to 6 GHz . What fraction of the period is skew, and why does this force a switch to serial?
Forecast: The period shrank by 60×. Guess: does skew now exceed a quarter of the period?
New period.
T c l k = 6 × 1 0 9 1 = 1.667 × 1 0 − 10 s = 166.7 ps
Why this step? Higher frequency = shorter period; the physical skew did not change, only the budget did.
Fraction lost.
166.7 44.4 = 0.266 = 26.6%
Why this step? Same skew, tiny period ⇒ skew now devours over a quarter of every bit window.
Verify: 26.6% > 15% danger line → the bus cannot sample reliably . This is exactly why designers move to a single differential serial lane where multi-wire alignment vanishes. Sanity: skew fraction from Ex 1 was 0.44%; multiplying frequency by 60 multiplies the fraction by 60 → 0.44% × 60 = 26.6% . ✓
Worked example The impossible perfect PCB
Suppose a magical PCB makes all traces exactly equal length, so Δ t s k e w = 0 . With t se t u p = 30 ps and t h o l d = 20 ps , what is the maximum parallel clock frequency?
Forecast: With zero skew, is the speed limit infinite, or does something else still cap it?
Recall the period floor (from the parent's skew formula):
T c l k ≥ Δ t s k e w + t se t u p + t h o l d
Why this step? Even with perfect traces, the flip-flop still needs setup + hold time to latch.
Substitute zero skew.
T c l k ≥ 0 + 30 + 20 = 50 ps
Why this step? This is the degenerate input the matrix demands — it shows skew is not the only limit.
Invert for frequency.
f ma x = 50 × 1 0 − 12 1 = 2.0 × 1 0 10 Hz = 20 GHz
Verify: Even the perfect bus caps at 20 GHz because of setup+hold. Units: 1/ s = Hz . ✓ Sanity: removing skew raised the limit but did not make it infinite — exactly the lesson of a degenerate-input check.
Worked example A 3 Gbaud lane with 8b/10b
A serial lane transmits at symbol rate R s = 3 Gbaud using NRZ (b = 1 bit/symbol) and 8b/10b encoding . What is the usable data rate?
Forecast: 8b/10b sends 10 bits for every 8 data bits. Guess the efficiency and the final Gbps.
Find efficiency.
η = n k = 10 8 = 0.8
Why this step? 2 of every 10 transmitted bits carry no user data — they buy DC balance and clock edges for the CDR.
Apply the data-rate engine.
R d a t a = R s ⋅ η ⋅ b = 3 × 1 0 9 × 0.8 × 1 = 2.4 × 1 0 9 bps = 2.4 Gbps
Why this step? Symbols/sec × (fraction that's real data) × (bits/symbol) = user bits/sec.
Verify: 3 Gbaud → 2.4 Gbps ; you paid 20% for the encoding. Units: Gbaud×(dimensionless)×(bits/symbol)=Gbps. ✓ This is exactly the SATA / USB 3.0 style overhead.
Worked example PCIe Gen3 lane efficiency
A PCIe Gen3 lane runs at R s = 8.0 GT/s with 128b/130b encoding, NRZ. Compute the per-lane data rate.
Forecast: 130 bits carry 128 real ones — barely any waste. Guess above or below 7.9 Gbps.
Efficiency.
η = 130 128 = 0.98462
Why this step? Modern encodings tack the sync bits onto a big block, so overhead drops from 20% to ~1.5%.
Data rate.
R d a t a = 8.0 × 1 0 9 × 130 128 × 1 = 7.877 × 1 0 9 bps = 7.877 Gbps
Verify: Matches the parent note's 7.877 Gbps figure exactly. ✓ Compare Ex 4: same idea, far less tax — that's the whole reason PCIe abandoned 8b/10b after Gen2.
Worked example A full x16 slot
Using the per-lane 7.877 Gbps from Ex 5, what is the aggregate throughput of a 16-lane (x16) PCIe Gen3 link?
Forecast: Lanes are independent; guess the total in Gbps and whether it beats a 64-bit parallel bus.
Multiply lanes (they carry independent data in parallel).
R t o t a l = 16 × 7.877 = 126.03 Gbps
Why this step? Each serial lane is its own differential pair ; total bandwidth is a clean sum with no shared clock to skew.
Verify: ≈126 Gbps over 16 pairs (32 wires). A 64-bit parallel bus would need 64 wires and still be skew-limited near 1 GHz. ✓ Matches parent's "~126 Gbps total".
Worked example Perfectly matched crystals
Transmitter and receiver share the exact same reference frequency, so the sampling clock never drifts. With ideal signaling, what phase error must the CDR correct, and does the link still need a CDR?
Forecast: Zero drift — is the CDR now useless?
Frequency offset is zero , so the accumulated timing error from drift is 0 ps .
Why this step? Drift error grows as (frequency difference)×(time); with zero difference, it's flat zero.
But there is still no separate clock wire. The receiver must find mid-bit once at start-up.
Why this step? This degenerate case shows the CDR's job splits into two: (a) track drift — now 0 , and (b) find the initial sampling phase — still required.
Verify: Even with 0 drift, the CDR is still needed to acquire phase; only the tracking load drops to zero. Sanity check against Ex 8: the drift budget there is what shrinks to nothing here.
Worked example USB 3.0 half-bit rule
USB 3.0 runs at 5 Gbps (NRZ, so 1 symbol = 1 bit). Compute the bit period and the maximum allowed CDR phase error.
Forecast: The rule is "sample within half a bit". Guess T bi t and the half-bit window in ps.
Bit period.
T bi t = R s 1 = 5 × 1 0 9 1 = 2.0 × 1 0 − 10 s = 200 ps
Why this step? Bit rate and bit period are reciprocals; this sets the whole timing budget.
Apply the half-bit rule (from the parent's CDR formula):
∣Δ ϕ ∣ < 2 T bi t = 2 200 = 100 ps
Why this step? Sample later than mid-bit by more than half and you land in the next bit — a guaranteed error.
Verify: 100 ps window matches the parent's stated USB 3.0 budget. ✓ Their measured Δ ϕ ≈ ± 10 ps sits comfortably inside 100 ps. Units: 1/ ( bits/s ) = s/bit . ✓
Worked example "Cable or PCB?" engineering decision
You must move 10 Gbps of user data between two chips 12 cm apart. Option A: a 16-bit parallel bus. Option B: a single serial lane at 12.5 Gbaud NRZ with 8b/10b. (a) Does Option B meet the 10 Gbps requirement? (b) For Option A, what per-wire skew results from a 6 mm mismatch, and what clock would 16 wires need?
Forecast: Bet on serial winning; guess whether the parallel clock lands in a comfortable or scary range.
Serial usable rate (Option B).
R d a t a = 12.5 × 1 0 9 × 0.8 × 1 = 10.0 × 1 0 9 = 10.0 Gbps
Why this step? Check the requirement directly with the data-rate engine; 8b/10b ⇒ η = 0.8 .
Serial verdict: 10.0 Gbps = requirement → meets it exactly on one differential pair.
Parallel skew (Option A).
Δ t s k e w = 1.8 × 1 0 8 6 × 1 0 − 3 = 3.33 × 1 0 − 11 = 33.3 ps
Why this step? Parallel's enemy is skew; convert the mismatch to time.
Parallel clock needed. 16 wires carrying 10 Gbps total need 10/16 = 0.625 Gbps per wire , i.e. 625 MHz , period 1600 ps . Skew fraction:
1600 33.3 = 2.08%
Why this step? We must confirm the skew is tolerable at the required clock.
Verify: Serial hits 10.0 Gbps on 2 wires; parallel hits it on 16 wires with 2.08% skew — technically fine but 8× the pin count and EMI. Choose serial (Option B). Units all consistent (ps/ps, Gbps). ✓
Worked example Where does parallel "die"?
Define parallel as unusable once skew reaches 25% of the clock period. For a bus with fixed skew Δ t s k e w = 40 ps , find the clock frequency at which parallel dies (the limiting value).
Forecast: Solve for the period where 40 ps is exactly a quarter of it, then invert. Guess the GHz.
Set the limiting condition.
T c l k Δ t s k e w = 0.25 ⇒ T c l k = 0.25 Δ t s k e w = 0.25 40 = 160 ps
Why this step? "Dies at 25%" is an equation; solving it gives the exact period boundary — the limiting value the matrix wants.
Invert to frequency.
f d i e = 160 × 1 0 − 12 1 = 6.25 × 1 0 9 Hz = 6.25 GHz
Why this step? Below 6.25 GHz parallel is fine; above it, this bus is dead — the crossover to serial.
Verify: Below 6.25 GHz → skew < 25% → OK; above → parallel unusable. Cross-check with Ex 2: at 6 GHz the 44.4 ps bus was at 26.6% (already dead), consistent since its skew exceeds 40 ps. ✓ Units: 1/ s = Hz . ✓
Recall Self-test — cover the answers
USB 3.0 at 5 Gbps: bit period? ::: 200 ps , so CDR window = 100 ps .
8b/10b efficiency and its cost? ::: η = 0.8 ; you pay 20% overhead for DC balance + edges.
PCIe Gen3 per-lane rate? ::: 8.0 × 130 128 = 7.877 Gbps .
Why doesn't zero skew give infinite parallel speed (Ex 3)? ::: setup + hold still floor the period (here 50 ps → 20 GHz).
Crossover speed for a 40 ps-skew bus at the 25% rule? ::: 6.25 GHz .
Mnemonic The whole page in one line
"Skew scales with speed, data scales with η — pick the engine, plug the number, check the fraction."
See also: Equalization (CTLE, DFE) and PLL and Clock Synthesis for how real receivers widen the sampling window these examples assumed, and the DDR Memory Interface for the modern parallel bus that fights skew with per-bit training.