PCIe Series — PCIe-30: PCIe 5.0 NRZ, 6.0 PAM4, FEC and What Changed — VLSI Trainers
PCIe Series · PCIe-30

PCIe 5.0, 6.0 — NRZ, PAM4, FEC and What Changed

The full PCIe generation trajectory from 2.5 GT/s NRZ to 64 GT/s PAM4 — why each doubling required different physical layer engineering, how NRZ was pushed to 32 GT/s in Gen 5 purely through aggressive equalization, why the NRZ wall finally arrived at 64 GT/s forcing PAM4 in Gen 6, how Reed-Solomon FEC compensates for PAM4’s eye closure, and what the flit-based Transport Layer changes in Gen 6 mean for the stack.

The Bandwidth Trajectory

Every PCIe generation has approximately doubled the bandwidth per lane of the previous generation. Across eight generations spanning three decades this has produced a 128× bandwidth increase from the same physical connector and backward-compatible protocol stack. The challenge is that each doubling requires increasingly sophisticated signal integrity engineering at the Physical Layer.

PCIe Bandwidth per Lane per Direction — Generation by Generation Gen 1 2.5 GT/s 8b/10b 250 MB/s NRZ 2003 Gen 2 5 GT/s 8b/10b 500 MB/s NRZ 2007 Gen 3 8 GT/s 128b/130b 1 GB/s NRZ 2010 Gen 4 16 GT/s 128b/130b 2 GB/s NRZ 2017 Gen 5 32 GT/s NRZ 4 GB/s 128b/130b NRZ 2019 Gen 6 64 GT/s PAM4 8 GB/s Flit + RS-FEC 2022 Gen 7 128 GT/s? 16 GB/s? ~2026+ In development ×1 base ×2 ×4 ×8 ×16 ×32
Figure 1 — PCIe bandwidth per lane per direction across all generations. Gen 1–5 used NRZ (Non-Return-to-Zero) signalling. Only Gen 6 switched to PAM4. Gen 6 also introduced flit-based Transport Layer framing. Gen 7 is in development. The 32× bandwidth improvement from Gen 1 to Gen 6 comes from the same physical x16 PCIe slot — backward-compatible at the connector and software levels throughout.

📋 Gen 1 and Gen 2 — NRZ with 8b/10b

Gen 1 (2.5 GT/s) and Gen 2 (5 GT/s) use NRZ (Non-Return-to-Zero) signalling — the signal has exactly two levels: a logic-high voltage and a logic-low voltage. Each symbol carries one bit. The encoding is 8b/10b: every 8-bit data byte is mapped to a 10-bit code word before transmission. This 25% overhead (10 bits sent for every 8 bits of data) exists for three reasons:

The effective data rate: Gen 1 at 2.5 GT/s with 8b/10b → 2.5 × 0.8 / 8 = 250 MB/s per lane per direction. Gen 2 doubles to 5 GT/s → 500 MB/s per lane per direction.

📋 Gen 3 — 128b/130b and Equalisation

Gen 3 doubles the bit rate to 8 GT/s but replaces 8b/10b with 128b/130b encoding. The motivation: at 8 GT/s, the 25% overhead of 8b/10b wastes too much bandwidth. 128b/130b adds only 2 bits per 128-bit block (1.5% overhead), recovering almost all of 8b/10b’s waste and effectively doubling the data throughput even without doubling the raw bit rate.

128b/130b works differently from 8b/10b:

Gen 3 also introduces 3-tap transmitter equalization (pre-cursor, cursor, post-cursor coefficients) and more aggressive receiver equalization (CTLE — Continuous Time Linear Equalizer) to compensate for channel loss at 8 GT/s. Training sequences exchange equalization presets using new TS1/TS2 fields during link training.

Effective data rate: 8 GT/s with 128b/130b → 8 × (128/130) / 8 ≈ 984 MB/s ≈ 1 GB/s per lane per direction.

📋 Gen 4 — 16 GT/s NRZ at its Limit

Gen 4 doubles to 16 GT/s while keeping the same NRZ modulation and 128b/130b encoding as Gen 3. The doubling required significant signal integrity improvements:

Effective data rate: 16 GT/s × (128/130) / 8 ≈ 2 GB/s per lane per direction. A x16 Gen 4 link delivers 32 GB/s bidirectional — sufficient for NVMe SSDs and NVIDIA A100-class GPUs.

Gen 4 reached 16 GT/s NRZ and was widely adopted. However, a further direct NRZ doubling to 32 GT/s without significantly more aggressive equalization would be impractical on standard add-in card trace lengths. Gen 5 achieved 32 GT/s NRZ by applying significantly more aggressive equalization (no RS-FEC, no PAM4). The true NRZ wall arrived at 64 GT/s — the point where even the best equalization cannot open the NRZ eye — which is why Gen 6 was the first generation to switch to PAM4 and to introduce RS-FEC.

📋 The NRZ Wall — Why NRZ Cannot Reach 64 GT/s

Gen 5 achieved 32 GT/s NRZ with aggressive equalization. But doubling again to 64 GT/s with NRZ is where the physics becomes prohibitive — two compounding effects make it impractical at standard PCB trace lengths:

Why NRZ Cannot Scale to 64 GT/s — Two Physical Limits Channel Insertion Loss Doubles PCB dielectric loss ∝ frequency (Nyquist = half bit rate) Gen 3 Nyquist: 4 GHz · Gen 4 Nyquist: 8 GHz NRZ 64 GT/s Nyquist: 32 GHz → channel loss 2× Gen 5 Typical PCB: ~0.5 dB/GHz → 8 dB additional loss at 16 GHz Equalizer cannot fully compensate at add-in card lengths NRZ Eye Closes at 64 GT/s NRZ eye height ∝ 1/frequency — halves with each doubling Gen 4 16 GT/s already requires DFE to open the eye At 64 GT/s NRZ: eye height < 15 mV after 15 cm trace BER (Bit Error Rate) exceeds 10⁻⁶ — link non-functional No equalizer can reliably recover a closed NRZ eye
Figure 2 — The NRZ wall at 64 GT/s. Gen 5 achieved 32 GT/s NRZ with aggressive equalization (no RS-FEC). At 64 GT/s NRZ, the Nyquist frequency would be 32 GHz — above the 3 dB point of most PCB dielectrics. Channel loss on a 15 cm PCB trace at 32 GHz is typically 15–20 dB, far beyond what any equalizer can compensate. The NRZ eye at 64 GT/s closes completely on standard PCB traces. This is why Gen 6 switched to PAM4 at 64 GT/s rather than attempting NRZ — PAM4 keeps the Nyquist frequency at 32 GHz while carrying 2 bits per symbol, doubling throughput without doubling the symbol rate.

The PAM4 solution for Gen 6: instead of doubling the symbol rate (which would push Nyquist to 32 GHz and close the NRZ eye), keep the symbol rate at 32 GBaud but carry 2 bits per symbol. PAM4 uses four voltage levels — each symbol encodes 2 bits. The Nyquist frequency stays at 32 GHz (same as a 64 GT/s NRZ link would require), but now each symbol carries 2 bits — achieving 64 GT/s effective bit rate with a manageable channel bandwidth. PAM4 is the only viable path to 64 GT/s on standard PCB channels.

📋 PAM4 — Four Voltage Levels Per Symbol

PAM4 (Pulse Amplitude Modulation with 4 levels) uses four distinct voltage levels to encode 2 bits per symbol. The four levels (named by their Gray coding): 00b, 01b, 11b, 10b from most negative to most positive. Because each transmitted symbol now carries 2 bits instead of 1, twice the data rate can be achieved at the same symbol rate (same Nyquist frequency).

NRZ vs PAM4 — Same Symbol Rate, 2× Bit Rate NRZ — 2 Levels, 1 bit/symbol +V ─── 1 −V ─── 0 Same symbol interval → 1 bit carried PAM4 — 4 Levels, 2 bits/symbol +V3 ─ 11 +V1 ─ 10 −V1 ─ 01 −V3 ─ 00 Same symbol interval → 2 bits carried
Figure 3 — NRZ vs PAM4 at the same symbol rate. NRZ has two voltage levels (high/low) — one bit per symbol. PAM4 has four voltage levels (−V3, −V1, +V1, +V3) — two bits per symbol using Gray coding. Both use the same symbol interval (same Nyquist frequency), but PAM4 carries twice the data rate. The price: PAM4 has three eye openings instead of one, each only 1/3 the height of a full-swing NRZ signal — requiring FEC to maintain acceptable BER.

PAM4 Gray coding

PAM4 uses Gray coding to map 2-bit dibit values to voltage levels. Adjacent voltage levels differ by only one bit: 11→10→00→01 (reading from top to bottom voltage level). Gray coding minimises the number of bit errors when the signal amplitude is misinterpreted as an adjacent level — the most likely error — because a one-level slip causes only a 1-bit error rather than a 2-bit error.

📋 PAM4 Eye Diagrams and Signal Integrity

A PAM4 eye diagram shows three eye openings (between the four voltage levels) rather than the single eye opening of NRZ. Each eye’s height is roughly one-third of the full voltage swing — making each eye significantly smaller than an equivalent NRZ signal at the same symbol rate. This is the fundamental trade-off of PAM4: twice the bit rate at the cost of a more demanding signal integrity requirement.

PAM4 Eye Diagram — Three Eyes, Each 1/3 of NRZ Eye Height NRZ Eye — Single Opening Full swing eye height +V ─ −V ─ PAM4 Eye — Three Openings Eye 3 (top) Eye 2 (mid) Eye 1 (bot) Each eye ≈ 1/3 NRZ eye height
Figure 4 — Eye diagrams. Left: NRZ has one large eye between two voltage levels. Right: PAM4 has three eyes stacked between four voltage levels. Each PAM4 eye has approximately one-third the amplitude margin of the equivalent NRZ eye, making PAM4 substantially more sensitive to noise, crosstalk, and ISI (inter-symbol interference). This sensitivity is why FEC is mandatory for PAM4 — correcting the frequent bit errors that even a well-equalised PAM4 link will experience due to its tight amplitude margins.

📋 Forward Error Correction — The FEC Solution

Forward Error Correction (FEC) is a technique where the transmitter adds redundant check symbols to the data stream. If some symbols are received incorrectly (due to noise, ISI, or crosstalk), the receiver uses the redundant symbols to detect and correct the errors — without any retransmission. “Forward” means the correction uses only the received data; no feedback to the transmitter is needed.

Why RS-FEC is necessary for Gen 6 PAM4 but not for Gen 1–5 NRZ:

📋 Reed-Solomon FEC in PCIe 6.0

PCIe 6.0 uses Reed-Solomon (RS) FEC. This is not used in Gen 5 — RS-FEC is specific to Gen 6’s PAM4 modulation, where the smaller eye opening produces far higher raw BER than NRZ links can tolerate. Reed-Solomon operates on symbols (bytes or multi-bit groups) rather than individual bits, making it particularly efficient at correcting burst errors — which is the dominant error pattern in PAM4 links where a momentary amplitude disturbance tends to corrupt several consecutive symbols.

Reed-Solomon FEC — Codeword Structure PCIe 6.0 Reed-Solomon FEC — RS(272,258) — operates at flit boundary 258 Data Symbols (2064 bits of flit data) Payload: TLP data, headers, DLLP — the actual traffic 14 Parity Symbols FEC overhead (5.1%) RS(272,258): Can correct up to 7 symbol errors OR detect up to 14 symbol errors per codeword A symbol error is any bit pattern error within one 8-bit symbol. One symbol error = 1–8 bit errors. FEC corrects burst errors very efficiently.
Figure 5 — Reed-Solomon FEC codeword structure for PCIe 6.0. RS(272,258) means 272 total symbols per codeword: 258 data symbols and 14 parity symbols. The parity overhead is 14/272 = 5.1% — a small but non-zero reduction in effective throughput that is factored into the Gen 6 bandwidth numbers. The receiver can correct any 7-symbol error pattern within the codeword, regardless of which specific bits within each symbol are wrong.

FEC latency

RS-FEC adds latency at both the transmitter (must accumulate a full codeword before sending) and receiver (must receive and decode the full codeword before forwarding to the Data Link Layer). For PCIe Gen 6, RS-FEC latency is approximately 4–8 ns per link hop — a new source of latency that does not exist in Gen 1–5. For multi-hop topologies with switches, RS-FEC latency accumulates at each hop. This is why L0s exit latency is higher at Gen 6 compared to Gen 1–5 — each L0s exit must re-establish RS-FEC sync in addition to re-locking the CDR.

📋 Gen 5 — 32 GT/s NRZ with Advanced Equalization

PCIe 5.0 (ratified 2019) doubles Gen 4 bandwidth by pushing NRZ to 32 GT/s. Gen 5 does not use PAM4 and does not use Reed-Solomon FEC — it remains NRZ (two voltage levels, one bit per symbol), exactly like Gen 1–4. What makes 32 GT/s NRZ viable is significantly more aggressive equalization (additional DFE taps, stricter Tx pre-emphasis, tighter jitter budget) and 128b/130b encoding unchanged from Gen 3/4. Gen 5 is the last NRZ generation.

Key Gen 5 changes relative to Gen 4:

Effective bandwidth: 32 GT/s NRZ × 1 bit/symbol × 128/130 (encoding overhead) / 8 = approximately 3.94 GB/s ≈ 4 GB/s per lane per direction. For a x16 Gen 5 link: 16 lanes × 2 directions × 4 GB/s = 128 GB/s bidirectional.

📋 Gen 6 — 64 GT/s PAM4 Physical Layer

PCIe 6.0 (ratified 2022) is the first generation to use PAM4. It doubles the bandwidth of Gen 5 NRZ by switching modulation: the symbol rate stays at 32 GBaud (same Nyquist frequency as Gen 5), but each symbol carries 2 bits instead of 1. The effective bit rate is 64 GT/s. Physical Layer changes relative to Gen 5:

Effective bandwidth: for a x16 Gen 6 link: 16 lanes × 2 directions × 8 GB/s = 256 GB/s bidirectional. The 8 GB/s per lane per direction accounts for FEC and flit overhead (approximately 93% efficiency).

Gen 6 physical layer is the current performance frontier. At 64 GT/s PAM4 on a standard PCB, the Nyquist frequency is 32 GHz — above the 3 dB frequency of most PCB dielectrics. Reaching Gen 6 bit error rates requires co-packaged optics, active copper cables with retimers, or extremely controlled PCB routing. Systems like AMD Instinct MI300X and NVIDIA H100/H200 use Gen 5 (32 GT/s) on package-level interconnects and Gen 4/5 for host PCIe because Gen 6 requires additional signal integrity engineering beyond standard PCB traces.

📋 Flit-Based Transport Layer (Gen 6 Only)

Gen 6 introduces the most significant change to the PCIe protocol stack since Gen 3: a new flit-based (FLow unIt) Transport Layer that replaces the variable-length TLP-based framing used in Gen 1–5. This change is unique to Gen 6 and is designed specifically to improve efficiency at 64 GT/s.

In Gen 1–5, the Physical Layer sends: SKIP ordered sets (to compensate for clock differences) + framing tokens (SFRM, EFRM for each TLP) + the actual TLP header and data + LCRC. Each TLP is individually framed and CRC-protected. The overhead from framing tokens, SKIP ordered sets, and LCRC per TLP is small but meaningful at high symbol rates.

In Gen 6, the Physical Layer sends a continuous stream of fixed-size 256-byte flits. Multiple TLPs are packed into flits. A single flit may contain one large TLP, multiple small TLPs, or fractions of TLPs that span multiple flits. The CRC in Gen 6 (the RS-FEC check symbols) protects the entire flit — there is no per-TLP LCRC in flit mode.

Gen 1–5 Variable TLP Framing vs Gen 6 Fixed 256-Byte Flits Gen 1–5 SoS TLP1 header+data LCRC EoS SoS TLP2 header + data payload LCRC EoS SKP, IDLE, next TLP… Variable length per TLP. Per-TLP LCRC. Framing tokens (SoS/EoS) overhead. Gen 6 Hdr TLP1 (full) TLP2 (full) TLP3 part ← RS-FEC parity (14 symbols) + Flit CRC → 256 B Fixed 256-byte flit. Multiple TLPs per flit. No per-TLP LCRC. RS-FEC covers entire flit. Gen 6 flit packing eliminates per-TLP framing overhead → ~2% more efficient than 128b/130b at the same raw bit rate.
Figure 6 — Gen 1–5 variable TLP framing vs Gen 6 fixed 256-byte flits. In Gen 1–5, each TLP has its own Start/End tokens, LCRC, and is individually framed. In Gen 6, multiple TLPs are packed into one 256-byte flit with a single flit header and RS-FEC check symbols at the end. Small TLPs pack efficiently (e.g., 4-DW TLPs pack 8 per flit). Large TLPs span multiple flits. The per-TLP LCRC is eliminated — error detection is handled entirely by the FEC. This is the primary reason Gen 6 replaces 128b/130b with flit mode.

📋 Flit Mode vs Standard TLP Mode

PropertyStandard TLP Mode (Gen 1–5)Flit Mode (Gen 6)
Frame unitVariable-length TLP (12 B–4112 B)Fixed 256-byte flit
FramingSDS/EIOS/EDS tokens per TLPFlit header (2 B) per 256-byte flit
CRC per TLPYes — 4-byte LCRC per TLPNo — eliminated
Error correctionLCRC detects errors → ACK/NAK replayRS-FEC corrects errors → no replay needed for FEC-correctable errors
Skip ordered setsInserted periodically for elastic buffer managementFlit header contains elastic buffer management fields — no separate SKIP symbols
ACK/NAK protocolRequired — Data Link Layer ack/nak every TLP (via DLLP)Simplified — ACK/NAK still present but at flit granularity, not TLP granularity
Encoding overhead128b/130b: 1.54% overheadFEC: 5.1% overhead, but flit packing recovers more than 1.54%
Backward compatibleAll Gen 1–5 links use thisGen 6 links only — negotiated during link training
Software visibleNo (Physical Layer detail)No — TLPs still look identical to software; flit/no-flit is invisible above Physical Layer
Flit mode is invisible to the Transaction Layer and above. Device drivers, the OS, and any software that uses PCIe TLPs see exactly the same TLP format whether the link is running in flit mode (Gen 6) or standard mode (Gen 1–5). The flit packing and unpacking happens entirely within the Physical Layer of each link endpoint. This is why existing software stacks — Linux kernel PCIe drivers, Windows PCIe bus driver, device firmware — require no modification to run on Gen 6 hardware.

📋 Equalization — Tx and Rx

At Gen 5 and Gen 6 speeds, the channel (PCB trace + package trace + connector) causes severe inter-symbol interference (ISI) — a transmitted symbol’s energy spreads into adjacent symbol slots, distorting them. Equalization compensates for this distortion:

TechniqueWhereHow it worksGen 5/6 usage
Tx Pre-Emphasis (FFE)TransmitterFeed-forward equalizer. Boosts high-frequency components of the transmitted signal before the channel attenuates them. Controlled by C-1 (pre-cursor), C0 (cursor), C1 (post-cursor) tap coefficients.3–5 taps at Gen 5 NRZ. Extended range and more complex coefficient space at Gen 6 PAM4 (must manage four voltage level transitions independently).
CTLEReceiverContinuous Time Linear Equalizer. Analog filter that boosts high frequencies at the receiver input — inverse of channel frequency response. Passive compensation always on.Required at Gen 5/6. Higher gain needed at 32/64 GT/s.
DFEReceiverDecision Feedback Equalizer. Uses previous decoded symbols to subtract their ISI contribution from the current symbol. More powerful than CTLE for severe ISI but adds latency.Strongly recommended at Gen 5/6. More taps needed than Gen 4.
PAM4 Receiver DSPReceiverDigital Signal Processing for PAM4 level detection, per-level threshold calibration, and multi-level eye monitoring.Gen 6 only. Not present in Gen 5 NRZ designs. Gen 5 uses standard NRZ 2-level eye monitoring.

Equalization coefficients are negotiated during link training (the Gen 3+ equalization Phase 1/2/3 in the LTSSM Configuration and Recovery states). The link partner communicates its receiver’s preferred transmitter coefficients using TS1/TS2 fields. Gen 5/6 add more Phase iterations and a wider search space to find the optimal equalization operating point.

📋 Retimers and Redrivers

At Gen 5 and Gen 6 speeds, the PCIe channel insertion loss budget may not accommodate standard add-in card trace lengths (typically 12–20 cm on a motherboard plus a PCIe cable or riser). Retimers and Redrivers extend the channel reach:

Device typeHow it worksTransparent to protocol?Gen 5/6 requirement
RedriverLinear amplifier. Boosts the analog signal without regenerating it. Adds gain but does not recover clock or data — still subject to accumulated jitter. Simpler and lower latency.Fully transparentMay be sufficient for Gen 5 in short reach applications (<30 cm total)
RetimerFull CDR — Clock and Data Recovery. Recovers the clock and data from the incoming signal, regenerates a clean signal from scratch. Eliminates accumulated jitter. PCIe-spec compliant retimers participate in link training and equalization negotiation.Spec-defined transparent: appears as extending the channel but does not affect BDF addressing or topologyOften required for Gen 5 beyond 30 cm, and for most Gen 6 channel lengths

PCIe-spec retimers (defined from Gen 3 onwards) are specification-compliant active devices that participate in the LTSSM training. They pass TS1/TS2 ordered sets and handle equalization negotiations on each segment independently, allowing the overall channel to be split into shorter segments each with manageable insertion loss.

📋 Backward Compatibility

PCIe’s most powerful feature across all generations is backward compatibility. A Gen 6 device connected to a Gen 3 system will train the link to Gen 3 speeds (8 GT/s, 128b/130b, no FEC, no flit mode) and operate fully. A Gen 3 device in a Gen 6 system trains the link to Gen 3 speeds. Neither device loses functionality — only bandwidth is limited to the common generation.

PCIe Backward Compatibility — Link Trains to Common Generation Gen 6 device 64 GT/s capable Gen 3 slot 8 GT/s max Trains to Gen 3 Result: 8 GT/s link ✓ (backwards compatible) Gen 3 device 8 GT/s capable Gen 6 slot 64 GT/s capable Trains to Gen 3 Result: 8 GT/s link ✓ (backwards compatible) How Speed Negotiation Works 1. Both sides train to Gen 1 (2.5 GT/s) first — always works 2. Negotiate highest common speed via Link Cap registers 3. Speed change sequence: enter Recovery, retrain at new rate 4. If higher speed fails, fall back to next lower speed
Figure 7 — PCIe backward compatibility. Both directions work: a Gen 6 device in an older slot, or an older device in a Gen 6 slot. The link always trains to Gen 1 (2.5 GT/s) first — the guaranteed common ground — and then attempts to negotiate to the highest speed both sides support. Speed change is handled transparently in the LTSSM Recovery state. Software and drivers are unaware of the training — the link state machine handles it automatically.

📋 Generation Comparison Quick Reference

GenerationGT/sModulationEncodingFECGB/s / lane / dirx16 BW (bidir)Year
Gen 12.5NRZ8b/10bNone0.258 GB/s2003
Gen 25NRZ8b/10bNone0.516 GB/s2007
Gen 38NRZ128b/130bNone~132 GB/s2010
Gen 416NRZ128b/130bNone~264 GB/s2017
Gen 532NRZ128b/130bNone~4128 GB/s2019
Gen 664PAM4Flit modeRS-FEC~8256 GB/s2022
ItemValue / Rule
8b/10b overhead25% — 10 bits sent per 8 data bits. Used in Gen 1 and Gen 2 only.
128b/130b overhead1.54% — 2 sync header bits per 128 data bits. Used in Gen 3, Gen 4, and Gen 5 (all NRZ).
NRZ definitionNon-Return-to-Zero: 2 voltage levels, 1 bit per symbol. Used in Gen 1–4.
PAM4 definitionPulse Amplitude Modulation-4: 4 voltage levels, 2 bits per symbol (Gray coded). Used in Gen 6 only. Gen 5 uses NRZ.
PAM4 Nyquist frequencyEqual to half the symbol rate. Gen 6 PAM4 at 64 GT/s symbol rate: Nyquist = 32 GHz. (Gen 5 NRZ at 32 GT/s: Nyquist = 16 GHz — same as Gen 6 PAM4. This is the elegance of PAM4: Gen 6 doubles bit rate while keeping the same Nyquist frequency as Gen 5.)
PAM4 eye penaltyEach of the three eyes is ≈1/3 the height of an NRZ eye at the same symbol rate. Raw BER ≈10⁻⁵ to 10⁻⁶ vs NRZ 10⁻¹² before FEC.
RS-FEC purpose (Gen 6)Correct raw symbol errors from PAM4’s BER floor (~10⁻⁵–10⁻⁶) before they reach the Data Link Layer. Not needed for Gen 5 NRZ which achieves ~10⁻¹² raw BER through equalization alone.
Reed-Solomon FECSymbol-based error correction. Gen 6 only. RS(272,258): 14 parity symbols, corrects up to 7 symbol errors per codeword. Not used in Gen 5 (NRZ achieves sufficient BER via equalization).
RS-FEC overhead (Gen 6 only)5.1% — 14 parity symbols per 272-symbol codeword. Gen 5 has no FEC overhead.
RS-FEC latency penalty~4–8 ns per link hop (Gen 6 only). Accumulates in multi-hop topologies. Increases L0s exit latency vs Gen 1–5. Not present in Gen 5 NRZ.
Flit definitionFixed 256-byte Transport Layer unit introduced in Gen 6. Multiple TLPs packed per flit. No per-TLP LCRC — FEC handles error correction.
Flit mode visibilityTransparent to software and drivers. TLP format unchanged. Only Physical Layer and Data Link Layer implementation changes.
Backward compatibilityAlways maintained. Gen 6 hardware trains to Gen 1 with older links. Link speeds negotiated via Link Capability registers during Recovery.
Equalization (Gen 5)Tx FFE (3–5 taps), CTLE, DFE. NRZ 2-level — more aggressive than Gen 4 but standard NRZ eye monitoring. No PAM4 DSP.
Equalization (Gen 6)Tx FFE (extended range), CTLE, DFE, PAM4 multi-level DSP for 4-level threshold calibration. Three eyes must all be monitored independently.
Retimer recommendationOften required for Gen 5 >30 cm trace, and for most Gen 6 channel lengths. Spec-defined retimers participate in LTSSM training.
Gen 6 Physical Layer Cap ID002Ch — Physical Layer 64.0 GT/s Capability. Reports equalization status, FEC capability, L0p state.
Gen 5 Physical Layer Cap ID002Ah — Physical Layer 32.0 GT/s Capability.
Gen 7 statusIn development at PCI-SIG as of 2024. Target 128 GT/s. Technology path (higher PAM levels, coherent optics, or further PAM4 SI) not finalised publicly.
Scroll to Top