New v2 UALink specification aims to catch up to NVLink
The UALink Consortium has released version 2.0 of its open-source interconnect specification as a competitor to Nvidia's NVLink for AI workloads. The update introduces new features like the UALink 200G Data Link and Physical Layers, In-Network Compute, and support for chiplet-based SoCs. Despite these advancements, no UALink 1.0 products are yet available, leaving Nvidia with a significant market lead.
- ▪The UALink 2.0 specification separates the Data Link and Physical Layers to allow faster updates and scalability.
- ▪UALink 2.0 includes In-Network Compute, a Manageability Specification, and a Chiplet Specification to improve performance and integration.
- ▪No UALink 1.0 products are currently shipping, and Nvidia remains ahead with its NVLink technology and ecosystem partnerships.
- ▪Companies like MediaTek and SiFive are integrating NVLink into their designs, reinforcing Nvidia's dominance.
- ▪UALink may find an opportunity to close the gap by supporting optical connectivity as an alternative to copper-based networking.
- ▪The UALink Consortium aims to enable multi-vendor, heterogeneous AI environments through open standards.
Opening excerpt (first ~120 words) tap to expand
Nvidia still holds the upper hand, but UALink ‘remains desirable’ as a way to enable multi-vendor environments, says an analyst. Credit: Norman Chan / Shutterstock The UALink Consortium, an industry body developing an open source alternative to Nvidia’s NVLink interconnect standard for AI workloads, has just published version 2.0 of the UALink specification. With this release, UALink introduces the UALink 200G Data Link and Physical Layers (DL/PL) Specification 2.0, which separates the DL/PL Specification from the original UALink Common Specification, thus enabling the body to move quickly as new physical layers and speeds come into play, and removing the need to make changes to other of its specifications.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Network World.
Discussion
0 commentsMore from Network World
