NVIDIA NVLink 6.0
Fields
interconnect/nvlink-6Notes
Vera Rubin generation. HEADLINE CAPABILITY, the third required quantity for this generation: NVLink 6 doubles the LINK COUNT again, 18 -> 36, while the per-link rate per direction goes DOWN from 50 to 41.7 - so this is the first generation in the family where the per-GPU aggregate rose while the per-link rate fell, and it is the clearest demonstration that NVIDIA's scaling lever on this fabric has been link count far more often than SerDes rate. The stated capability is rack-scale: 72 GPUs as one non-blocking all-to-all compute fabric at 3 TB/s per GPU pair, 216 TB/s total, with 'control plane resilience, the ability to run with a partially populated rack, and hot-swapping of switch trays' as the generation's actual new feature set - those three operational properties, not the bandwidth, are what NVIDIA leads with on this generation. NVIDIA's own relative claim is '1.7x more bandwidth than the previous generation', consistent with 3000/1800 = 1.67, and '12x the bandwidth of PCIe Gen6'.
NVIDIA's official NVLink product page spec table (accessed and re-verified 2026-10-05) confirms 3,000 GB/s per GPU and 36 max links per GPU for Sixth Generation NVLink, marked preliminary. The 3,600 GB/s figure from Wikipedia (link-wikipedia-nvlink) has no first-party NVIDIA support and is not used - the rejection is recorded as gotcha w7n-nvlink-6-3600-gbps-has-no-first-party-source rather than left implicit. Internal consistency check: 72 GPUs x 3 TB/s = 216 TB/s matches the NVL72 rack total, and 36 x 41.67 x 2 = 3,000 closes the per-GPU identity. ROUNDING NOTE, since the stored value is rounded to one decimal: 41.7 x 36 x 2 = 3,002.4 rather than exactly 3,000, because the exact per-link per-direction rate is 3000 / 36 / 2 = 41.667 GB/s. The 2.4 GB/s gap is 0.08% and is an artefact of the stored precision, not a different figure; a reader reproducing the identity should divide the vendor aggregate by the link count rather than multiply the stored rounded value back up. This is the only record in the family where the stored per-link rate needs more than one decimal to reproduce the published aggregate exactly. Inference consequence: tensor-parallel sharding wants the highest per-direction fabric rate available, because every layer boundary ships activations across the link; at 1,500 GB/s per direction per GPU against Vera Rubin's memory bandwidth the fabric is no longer the limiting term for a 72-GPU domain. PROVENANCE 2026-10-05: the per-link figure is DERIVED, and this is the generation where the direction label matters most - the prose calls the same 3 TB/s 'bidirectional' while the spec table prints a bare '3,000 GB/s' with no qualifier, so the table read alone invites exactly the 2x error this repo has been corrupted by twice. See also w7n-nvlink-per-gpu-aggregate-vs-per-link-rate.
Cross-references
This record references no other records — it is a leaf. It is cited by 3.