# US 2026/0228169 A1 · Translating Between NVLink and CXL.cache for High-Performance and Low-Latency Access from GPUs to CPU Memory

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0228169 A1
- Document ID: US20260228169A1
- Status: Published application
- Kind: A1
- Application number: 19/632,305
- Filed: 2026-03-29
- Published: 2026-08-06
- Earliest claimed: 2023-12-13
- Assignees: UnifabriX Ltd.
- Applicants: UnifabriX Ltd.
- Inventors: Ronen Aharon Hyatt; Gaya Opal Hyatt; Ethan Sharon Hyatt; Gil Thieberger
- Web page: https://patentgrep.com/patent/US20260228169A1

## CPC

- G06F 13/4027: {using bus bridges (G06F13/4022 takes precedence)}
- G06F 13/4221: {being an input/output bus, e.g. ISA bus, EISA bus, PCI bus, SCSI bus}
- G06F 13/1668: {Details of memory controller}
- G06F 13/4022: {using switching circuits, e.g. switching matrix, connection or expansion network (G06F13/4009 takes precedence)}
- G06F 2213/0026: PCI express
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Translating between NVLink-based protocols and CXL.cache Device-to-Host (D2H) and Host-to-Device (H2D) messages enables memory access across different protocol domains. In some implementations, a resource provisioning unit (RPU) receives an NVLink-based request from a first entity via an NVLink interface, translates the NVLink-based request to a CXL.cache D2H request comprising an opcode and a physical address, sends the CXL.cache D2H request to a second entity, receives a CXL.cache H2D response comprising data, and sends an NVLink-based response comprising the data to the first entity. The translation may utilize CXL.cache as an intermediate protocol for accessing a processor's coherent interconnect. In other implementations, a computer receives a CXL.cache H2D request from a first entity, translates it to an NVLink-based request sent to a second entity, receives an NVLink-based response, translates the response to CXL.cache D2H messages, and sends the D2H messages to the first entity.

## Claims

### Claim 1

A method comprising:
receiving, by a resource provisioning unit (RPU) from a first entity via an NVLink interface that communicates according to an NVLink-based protocol, an NVLink-based request comprising a first physical address;
translating, by the RPU, the NVLink-based request to a CXL.cache Device-to-Host (D2H) request comprising an opcode and a second physical address, wherein CXL denotes Compute Express Link;
sending, by the RPU, the CXL.cache D2H request to a second entity;
receiving, by the RPU from the second entity, a CXL.cache Host-to-Device (H2D) response comprising data accessed via the second physical address; and
sending, by the RPU, an NVLink-based response comprising the data to the first entity.

### Claim 2 (depends on 1)

The method of claim 1, wherein the second entity comprises a CXL root port (RP) coupled to a coherent interconnect of a processor, and the data is retrieved via the coherent interconnect from at least one of: a cache of the processor, a memory controller coupled to memory, or a CXL memory expander.

### Claim 3 (depends on 2)

The method of claim 2, wherein the CXL RP is coupled to the coherent interconnect via an interconnect interface, and the coherent interconnect utilizes a protocol selected from at least one of: ARM CHI, Intel UPI, or AMD Infinity Fabric.

### Claim 4 (depends on 1)

The method of claim 1, wherein the translating comprises translating an NVLink Tag carried in the NVLink-based request to a command queue identifier (CQID) carried in the CXL.cache D2H request, and maintaining a mapping between the NVLink Tag and the CQID for correlating the CXL.cache H2D response with the NVLink-based response.

### Claim 5 (depends on 1)

The method of claim 1, wherein the translating comprises translating the NVLink-based request to CXL.cache D2H requests when the NVLink-based request specifies a data payload larger than a cacheline, and wherein each of the CXL.cache D2H requests comprises an opcode selected from RdOwn or RdShared.

### Claim 6 (depends on 1)

The method of claim 1, wherein the translating comprises translating the first physical address from a GPU physical address or an NVLink network address to a Host Physical Address (HPA) carried as the second physical address in the CXL.cache D2H request.

### Claim 7 (depends on 1)

The method of claim 1, wherein the RPU, the NVLink interface, and a CXL device are implemented in a chiplet within an integrated circuit (IC) package of a processor, and the second entity comprises a CXL root port (RP) of the processor.

### Claim 8 (depends on 1)

The method of claim 1, wherein the RPU presents as a CXL endpoint (CXL EP) to the second entity, the CXL EP comprising a Type-1 CXL device or a Type-2 CXL device, and wherein the opcode of the CXL.cache D2H request comprises RdCurr.

### Claim 9 (depends on 1)

The method of claim 1, wherein the opcode of the CXL.cache D2H request comprises RdCurr, and further comprising forwarding the data received via the CXL.cache H2D response to the first entity without caching it by the RPU, whereby the RPU provides I/O-coherent access to resources accessible via the second entity.

### Claim 10 (depends on 1)

The method of claim 1, wherein the RPU comprises a cache, and the opcode of the CXL.cache D2H request is selected from RdOwn, RdShared, or RdAny; further comprising storing the data received via the CXL.cache H2D response in the cache of the RPU; and further comprising receiving, by the RPU from the second entity, a CXL.cache H2D request comprising a snoop opcode targeting a cacheline stored in the cache, and sending, by the RPU, a CXL.cache D2H response to the second entity.

### Claim 11 (depends on 1)

A non-transitory computer-readable medium comprising instructions which, when executed by a processor, cause the processor to perform the method of claim 1.

### Claim 12 (depends on 1)

An active cable comprising first and second pluggable modules coupled by a physical medium; wherein the active cable further comprises hardware circuitry, integrated into the active cable, configured to perform the method of claim 1.

### Claim 13 (depends on 1)

An apparatus configured to operate as a switch, wherein the apparatus comprises switching circuitry and is configured to perform the method of claim 1.

### Claim 14

A system comprising:
a processor comprising a Compute Express Link (CXL) root port (RP), a coherent interconnect, and memory controllers; wherein the memory controllers are coupled to the coherent interconnect and coupled to memory;
a resource provisioning unit (RPU) comprising: an NVLink interface configured to communicate with an entity according to an NVLink-based protocol, and a CXL endpoint (CXL EP) coupled to the CXL RP; and
wherein the RPU is configured to translate between NVLink-based requests received via the NVLink interface and CXL.cache Device-to-Host (D2H) requests sent to the CXL RP, to enable the entity to access memory resources via the coherent interconnect.

### Claim 15 (depends on 14)

The system of claim 14, wherein the CXL EP comprises a Type-1 CXL device or a Type-2 CXL device, and the coherent interconnect utilizes a protocol selected from at least one of: ARM CHI, Intel UPI, or AMD Infinity Fabric.

### Claim 16 (depends on 14)

The system of claim 14, further comprising processing cores and a last level cache (LLC) coupled to the coherent interconnect, and wherein the CXL RP is coupled to the coherent interconnect via an interconnect interface.

### Claim 17 (depends on 14)

The system of claim 14, wherein the RPU, the NVLink interface, and the CXL EP are on a first silicon die, and the CXL RP and the coherent interconnect are on a second silicon die, the first and second silicon dies within an IC package.

### Claim 18 (depends on 14)

The system of claim 14, wherein the RPU is further configured to translate CXL.cache Host-to-Device (H2D) requests received from the CXL RP to NVLink-based requests sent to the entity via the NVLink interface, enabling the processor to access resources of the entity.

### Claim 19

A method comprising:
receiving, by a computer from a first entity, a CXL.cache Host-to-Device (H2D) request comprising an opcode and a first address, wherein CXL denotes Compute Express Link;
translating, by the computer, the CXL.cache H2D request to an NVLink-based request comprising a second physical address;
sending, by the computer via an NVLink interface that communicates according to an NVLink-based protocol, the NVLink-based request to a second entity;
receiving, by the computer from the second entity, an NVLink-based response; and
translating, by the computer, the NVLink-based response to one or more CXL.cache Device-to-Host (D2H) messages, and sending the one or more CXL.cache D2H messages to the first entity.

### Claim 20 (depends on 19)

The method of claim 19, wherein the translating of the CXL.cache H2D request comprises translating a Unique Queue ID (UQID) carried in the CXL.cache H2D request to an NVLink Tag carried in the NVLink-based request, and maintaining a mapping between the UQID and the NVLink Tag for correlating the NVLink-based response with the one or more CXL.cache D2H messages.

### Claim 21 (depends on 19)

The method of claim 19, wherein the opcode of the CXL.cache H2D request comprises a snoop opcode selected from SnpData, SnpInv, or SnpCur, the NVLink-based request comprises a read or invalidation request type corresponding to the snoop opcode, the first entity comprises a CXL host, and the second entity comprises a GPU, an NVLink switch, or an accelerator.

### Claim 22 (depends on 19)

The method of claim 19, wherein the NVLink-based response comprises data, and the one or more CXL.cache D2H messages comprise a CXL.cache D2H response comprising a snoop response opcode and a Unique Queue ID (UQID), and a CXL.cache D2H Data comprising the data and the UQID.

### Claim 23 (depends on 19)

The method of claim 19, further comprising issuing, by the computer via the NVLink interface, additional NVLink-based requests to the second entity as prefetch requests based on a detected access pattern of CXL.cache H2D requests received from the first entity.

### Claim 24 (depends on 19)

A non-transitory computer-readable medium comprising instructions which, when executed by a processor, cause the processor to perform the method of claim 19.

### Claim 25 (depends on 19)

One or more integrated circuits configured to perform the method of claim 19, wherein the one or more integrated circuits comprise at least one of: (i) a general-purpose processing unit, comprising or connected to communication interfaces, configured to perform the method via software and/or firmware execution, (ii) circuitry comprising firmware and/or hardware logic integrated into an electronic device, wherein the circuitry utilizes operations that benefit from hardware acceleration and/or specialized processing capabilities not typically provided by a general-purpose processing unit, or (iii) one or more chiplets within one or more integrated circuit packages.

### Claim 26 (depends on 19)

An active cable comprising first and second pluggable modules coupled by a physical medium; wherein the active cable further comprises hardware circuitry, integrated into the active cable, configured to perform the method of claim 19.

### Claim 27

A system comprising:
a first interface configured to communicate according to CXL.cache with a first entity, wherein CXL denotes Compute Express Link;
a second interface configured to communicate according to an NVLink-based protocol with a second entity; and
a computer coupled between the first and second interfaces, configured to translate CXL.cache Host-to-Device (H2D) requests received via the first interface to NVLink-based requests transmitted via the second interface, and to translate NVLink-based responses received via the second interface to CXL.cache Device-to-Host (D2H) messages transmitted via the first interface.

### Claim 28 (depends on 27)

The system of claim 27, wherein the CXL.cache D2H messages comprise a CXL.cache D2H response comprising an opcode selected from RspSFwdM, RspIFwdM, or RspVFwdV, and a CXL.cache D2H Data comprising data sourced from a memory or a cache of the second entity.

### Claim 29 (depends on 27)

The system of claim 27, wherein the computer is configured to translate Host Physical Addresses (HPAs) carried in the CXL.cache H2D requests to NVLink network addresses or GPU physical addresses carried in the NVLink-based requests.

### Claim 30 (depends on 27)

The system of claim 27, wherein the computer is included in a switch or a bridge, and the computer is further configured to translate NVLink-based requests received via the second interface to CXL.cache D2H requests transmitted via the first interface, enabling the second entity to access resources coupled to the first entity.
