inference/research
verifiedhigh · 0.85updated 2026-10-05

PCI Express 7.0

242.0 GB/s

Fields

id
interconnect/pcie-gen7
Kind
pcie
Version
7.0 (128 GT/s, PAM4/FLIT)
Bandwidth (GB/s, per link, unidirectional)
242
Bandwidth basis
x16, PER DIRECTION (payload, post 242B/256B flit framing). THE CONVENTION, STATED EXPLICITLY BECAUSE THIS RECORD IS THE ONE MOST LIKELY TO BE HALVED TWICE: PCIe figures are quoted PER LANE PER DIRECTION and a PCIe lane is dual-simplex, so a per-direction figure is ALREADY complete for its direction and must never be halved again. PCI-SIG's own wording for this generation (w7p-pcisig-pcie7-release-pr), verbatim: 'Delivers 128.0 GT/s raw bit rate and up to 512 GB/s BI-DIRECTIONALLY via x16 configuration.' 512 is therefore the BIDIRECTIONAL RAW figure; the per-direction RAW figure is 256.0 GB/s. Storing 512.0 as if it were per-direction is a 2x ERROR that doubles the interconnect; storing the 256.0 per-direction raw figure as an aggregate is the same error inverted. THE THREE FIGURES FOR THIS GENERATION, kept distinct because conflating them is the failure: 256.0 GB/s = raw per direction (PCI-SIG's 512 / 2); 242.0 GB/s = PAYLOAD per direction (this stored value); 484.0 GB/s = payload bidirectional aggregate (242 x 2). Derivation: 128 GT/s x 242/256 flit framing = 121.0 Gb/s payload per lane per direction; / 8 = 15.125 GB/s per lane per direction; x16 = 242.0 GB/s per direction. PCI-SIG does NOT publish the 242/256 framing efficiency or any payload figure on its own pages - it publishes the raw 512 bidirectional only - so the framing ratio is cited to w7p-wikipedia-pcie-link-performance, whose table row reads '7.0 | 2025 (specification released) | 128.0 GT/s | 15.125 | 30.25 | 60.5 | 121 | 242' with the column footnote 'In each direction (each lane is a dual simplex channel).' That table reproduces exactly under 'GT/s x efficiency / 8 x 16' with no extra halving, which independently confirms the per-direction reading. CROSS-CHECK THAT PROVES THE CONVENTION: PCI-SIG's 512 GB/s bidirectional is exactly 128 GT/s x 16 lanes / 8 x 2 directions, so the factor of two is already inside PCI-SIG's number and must not be applied to it again; and the one generation down, PCIe 6.0's per-direction raw is 128.0 (w7p-pcisig-pcie6-faq), exactly half of this generation's 256.0 - the clean x2 that PCI-SIG's 'doubling ... every three years' claim requires.
Link count
16
Topology
Point-to-point host-to-device, up to 16 lanes, with flit-level framing and PAM4 signalling as PCIe 6.0. PCI-SIG publishes link widths of 1, 2, 4, 8, 12, 16 and 32 (w7p-pcisig-pcie5-faq-verified); x16 is used here for comparability across the pcie-gen* family, not because it is the maximum. Shares the physical layer with CXL 5.0.
Scale-up
yes
Scale-out
no
Switching
Optional PCIe switch fabric, as for PCIe 6.0 - store-and-forward, no in-network compute or reduction.
notes
WHY BANDWIDTH JUMPS NON-LINEARLY VERSUS GT/s - THE POINT A GT/s-ONLY COMPARISON GETS WRONG, stated because it is this repo's second recurring error mode after the direction convention. From PCIe 5.0 to PCIe 6.0 the GT/s rate doubles (32 -> 64) and the RAW bidirectional figure doubles with it (128 -> 256 GB/s), but the PAYLOAD per direction goes 63.0 -> 121.0 GB/s, a ratio of 1.92x, NOT 2x. The missing 4% is the encoding change: PCIe 1.0-5.0 use NRZ with 128b/130b line coding (98.46% efficiency), whereas PCIe 6.0 and 7.0 use PAM4 with 242B/256B flit framing (94.53% efficiency). PAM4 carries two bits per symbol instead of one - PCI-SIG, verbatim: 'NRZ uses two levels of signaling, while PAM4 uses four levels. It packs two bits of information into the same amount of time on a serial channel' (w7p-pcisig-pcie6-faq). A reader who compares Gen5 to Gen6 by GT/s alone would compute 32 -> 64 and conclude 'exactly double', then find the real payload is 1.92x and conclude one of the records is wrong. Both are right; the framing overhead is real and is the entire discrepancy. The corollary in the other direction: Gen6 -> Gen7 IS exactly 2.00x on payload per direction (121.0 -> 242.0) because the framing is unchanged between them - so PAM4 makes the FIRST post-NRZ step non-linear and every subsequent step linear again, and any table of this family that shows a uniform 2x per generation is either quoting raw rates or has silently mixed conventions. SECOND COST OF PAM4, from the same PCI-SIG FAQ, verbatim: 'the bit error rate (BER) was several orders of magnitude higher than the 10-12 BER in all prior generations' and 'Flit Mode supports the higher BER expected in PAM4 (10-6 vs 10-12 in NRZ)' - so Gen6/Gen7 require FEC and CRC, and are a materially different signal-integrity and retimer problem from Gen5. INFERENCE CONSEQUENCE: at 242.0 GB/s per direction, PCIe 7.0 x16 finally exceeds NVLink 4's 450 GB/s per direction... note that it does NOT - it remains roughly 1.9x below it, the same ratio as Gen6, because PCIe and NVLink are on different ladders. What PCIe 7.0 does change is that a tensor-parallel group over a PCIe host attach becomes far less absurd than at Gen5: PCIe 7.0 is the first generation where the host link is no longer the dominant bottleneck for weight streaming on a large model. Deployment reality check, because a spec release is not silicon: PCI-SIG's own framing of the generation is future-facing, and Ian Cutress (More Than Moore) is quoted as saying 'Datacenters are ready to start deploying networks built on PCIe 7.0 technology' - intent, not shipments. No accelerator in data/accelerators/ in this repo is recorded as attaching over PCIe 7.0, so this record is a spec-generation fact with no measured consumer yet. Revision currency: PCIe 7.0 reached FINAL specification on 11 June 2025 (w7p-pcisig-pcie7-release-pr), so it is published, but per the same release 'Pathfinding for the PCIe 8.0 specification is already in progress' at 256.0 GT/s.
way
each

Notes

WHY BANDWIDTH JUMPS NON-LINEARLY VERSUS GT/s - THE POINT A GT/s-ONLY COMPARISON GETS WRONG, stated because it is this repo's second recurring error mode after the direction convention. From PCIe 5.0 to PCIe 6.0 the GT/s rate doubles (32 -> 64) and the RAW bidirectional figure doubles with it (128 -> 256 GB/s), but the PAYLOAD per direction goes 63.0 -> 121.0 GB/s, a ratio of 1.92x, NOT 2x. The missing 4% is the encoding change: PCIe 1.0-5.0 use NRZ with 128b/130b line coding (98.46% efficiency), whereas PCIe 6.0 and 7.0 use PAM4 with 242B/256B flit framing (94.53% efficiency). PAM4 carries two bits per symbol instead of one - PCI-SIG, verbatim: 'NRZ uses two levels of signaling, while PAM4 uses four levels. It packs two bits of information into the same amount of time on a serial channel' (w7p-pcisig-pcie6-faq). A reader who compares Gen5 to Gen6 by GT/s alone would compute 32 -> 64 and conclude 'exactly double', then find the real payload is 1.92x and conclude one of the records is wrong. Both are right; the framing overhead is real and is the entire discrepancy. The corollary in the other direction: Gen6 -> Gen7 IS exactly 2.00x on payload per direction (121.0 -> 242.0) because the framing is unchanged between them - so PAM4 makes the FIRST post-NRZ step non-linear and every subsequent step linear again, and any table of this family that shows a uniform 2x per generation is either quoting raw rates or has silently mixed conventions. SECOND COST OF PAM4, from the same PCI-SIG FAQ, verbatim: 'the bit error rate (BER) was several orders of magnitude higher than the 10-12 BER in all prior generations' and 'Flit Mode supports the higher BER expected in PAM4 (10-6 vs 10-12 in NRZ)' - so Gen6/Gen7 require FEC and CRC, and are a materially different signal-integrity and retimer problem from Gen5. INFERENCE CONSEQUENCE: at 242.0 GB/s per direction, PCIe 7.0 x16 finally exceeds NVLink 4's 450 GB/s per direction... note that it does NOT - it remains roughly 1.9x below it, the same ratio as Gen6, because PCIe and NVLink are on different ladders. What PCIe 7.0 does change is that a tensor-parallel group over a PCIe host attach becomes far less absurd than at Gen5: PCIe 7.0 is the first generation where the host link is no longer the dominant bottleneck for weight streaming on a large model. Deployment reality check, because a spec release is not silicon: PCI-SIG's own framing of the generation is future-facing, and Ian Cutress (More Than Moore) is quoted as saying 'Datacenters are ready to start deploying networks built on PCIe 7.0 technology' - intent, not shipments. No accelerator in data/accelerators/ in this repo is recorded as attaching over PCIe 7.0, so this record is a spec-generation fact with no measured consumer yet. Revision currency: PCIe 7.0 reached FINAL specification on 11 June 2025 (w7p-pcisig-pcie7-release-pr), so it is published, but per the same release 'Pathfinding for the PCIe 8.0 specification is already in progress' at 256.0 GT/s.

Cross-references

This record references no other records — it is a leaf. It is cited by 4.