dynamo/docs/API/nixl_connect

Dynamo NIXL Connect

Dynamo connect provides utilities for using the NIXL base RDMA subsystem via a set of Python classes. The primary goal of this library to simplify the integration of NIXL based RDMA into inference applications. The dynamo.nixl_connect library can be imported by any Dynamo container hosted application.

import dynamo.nixl_connect

All operations using the NIXL Connect library begin with the Connector class and the type of operation required. There are four types of supported operations:

1. Register local readable memory:

   Register local memory buffer(s) with the RDMA subsystem to enable a remote worker to read from.

2. Register local writable memory:

   Register local memory buffer(s) with the RDMA subsystem to enable a remote worker to write to.

3. Read from registered, remote memory:

   Read remote memory buffer(s), registered by a remote worker to be readable, into local memory buffer(s).

4. Write to registered, remote memory:

   Write local memory buffer(s) to remote memory buffer(s) registered by a remote worker to writable.

By connecting correctly paired operations, high-throughput GPU Direct RDMA data transfers can be completed. Given the list above, the correct pairing of operations would be 1 & 3 or 2 & 4. Where one side is a "(read|write)-able operation" and the other is its correctly paired "(read|write) operation". Specifically, a read operation must be paired with a readable operation, and a write operation must be paired with a writable operation.

sequenceDiagram
    participant LocalWorker
    participant RemoteWorker
    participant NIXL

    LocalWorker ->> NIXL: Register memory (Descriptor)
    RemoteWorker ->> NIXL: Register memory (Descriptor)
    LocalWorker ->> LocalWorker: Create Readable/WritableOperation
    LocalWorker ->> RemoteWorker: Send RDMA metadata (via HTTP/TCP+NATS)
    RemoteWorker ->> NIXL: Begin Read/WriteOperation with metadata
    NIXL -->> RemoteWorker: Data transfer (RDMA)
    RemoteWorker -->> LocalWorker: Notify completion (unblock awaiter)

Examples

Generic Example

In the diagram below, Local creates a WritableOperation intended to receive data from Remote. Local then sends metadata about the requested RDMA operation to Remote. Remote then uses the metadata to create a WriteOperation which will perform the GPU Direct RDMA memory transfer from Remote's GPU memory to Local's GPU memory.

---
title: Write Operation Between Two Workers
---
flowchart LR
  c1[Remote] --"3: .begin_write()"--- WriteOperation
  WriteOperation e1@=="4: GPU Direct RDMA"==> WritableOperation
  WritableOperation --"1: .create_writable()"--- c2[Local]
  c2 e2@--"2: RDMA Metadata via HTTP"--> c1
  e1@{ animate: true; }
  e2@{ animate: true; }

Multimodal Example

In the case of the Dynamo Multimodal Disaggregated Example:

1. The HTTP frontend accepts a text prompt and a URL to an image.

2. The prompt and URL are then enqueued with the Processor before being dispatched to the first available Decode Worker.

3. Decode Worker then requests a Prefill Worker to provide key-value data for the LLM powering the Decode Worker.

4. Prefill Worker then requests that the image be processed and provided as embeddings by the Encode Worker.

5. Encode Worker acquires the image, processes it, performs inference on the image using a specialized vision model, and finally provides the embeddings to Prefill Worker.

6. Prefill Worker receives the embeddings from Encode Worker and generates a key-value cache (KV$) update for Decode Worker's LLM and writes the update directly to the GPU memory reserved for the data.

7. Finally, Decode Worker performs the requested inference.

---
title: Multimodal Disaggregated Workflow
---
flowchart LR
  p0[HTTP Frontend] i0@--"text prompt"-->p1[Processor]
  p0 i1@--"url"-->p1
  p1 i2@--"prompt"-->dw[Decode Worker]
  p1 i3@--"url"-->dw
  dw i4@--"prompt"-->pw[Prefill Worker]
  dw i5@--"url"-->pw
  pw i6@--"url"-->ew[Encode Worker]
  ew o0@=="image embeddings"==>pw
  pw o1@=="kv_cache updates"==>dw
  dw o2@--"inference results"-->p0

  i0@{ animate: true; }
  i1@{ animate: true; }
  i2@{ animate: true; }
  i3@{ animate: true; }
  i4@{ animate: true; }
  i5@{ animate: true; }
  i6@{ animate: true; }
  o0@{ animate: true; }
  o1@{ animate: true; }
  o2@{ animate: true; }

[!Note] In this example, it is the data transfer between the Prefill Worker and the Encode Worker that utilizes the Dynamo NIXL Connect library. The KV Cache transfer between Decode Worker and Prefill Worker utilizes the NIXL base RDMA subsystem directly without using the Dynamo NIXL Connect library.

Code Examples

See prefill_worker or decode_worker from our Multimodal example, for how they coordinate directly with the Encode Worker by creating a WritableOperation, sending the operation's metadata via Dynamo's round-robin dispatcher, and awaiting the operation for completion before making use of the transferred data.

See encode_worker from our Multimodal example, for how the resulting embeddings are registered with the RDMA subsystem by creating a Descriptor, a WriteOperation is created using the metadata provided by the requesting worker, and the worker awaits for the data transfer to complete for yielding a response.

Python Classes

• Connector
• Descriptor
• Device
• ReadOperation
• ReadableOperation
• SerializedRequest
• WritableOperation
• WriteOperation

References

• NVIDIA Dynamo @ GitHub
  • NVIDIA Dynamo NIXL Connect
• NVIDIA Inference Transfer Library (NIXL) @ GitHub
• Dynamo Multimodal Example
• NVIDIA GPU Direct