{
  "status": "shipping",
  "advantages": [],
  "limitations": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-10-17",
  "slug": "nvme-rdma",
  "term": "NVMe/RDMA",
  "aliases": [
    "NVMe over RDMA"
  ],
  "definition": "NVMe/RDMA is an NVMe transport binding that uses reliable RDMA queue pairs for capsule delivery and direct data placement.",
  "note": "Transport scope: The binding supports RDMA providers such as InfiniBand, RoCE and iWARP. It excludes unreliable queue-pair modes [rdma].\n\nLayering: iWARP operates over TCP/IP, but it still carries the NVMe/RDMA binding rather than NVMe/TCP. Requirements of one provider must not be attributed to every RDMA network [rdma].\n\nDeployment: An RDMA implementation needs compatible adapters, drivers and memory-registration resources. Direct placement does not establish a workload-independent latency advantage [spdk].",
  "related": [
    "nvme-of",
    "rdma-storage",
    "nvme-tcp",
    "nvme-fc",
    "nvme-discovery-controller"
  ],
  "citations": [
    {
      "id": "rdma",
      "title": "NVM Express NVMe over RDMA Transport 1.3, section 2",
      "url": "https://nvmexpress.org/wp-content/uploads/NVM-Express-NVMe-over-RDMA-Transport-Specification-Revision-1.3-Ratified-2026.07.31.pdf",
      "accessed": "2026-10-17"
    },
    {
      "id": "spdk",
      "title": "SPDK NVMe over Fabrics target: transport support, TLS and in-band authentication",
      "url": "https://spdk.io/doc/nvmf.html",
      "accessed": "2026-10-17"
    }
  ],
  "provenance": [
    "Protocol scope is pinned to RDMA Transport 1.3. Adapter and memory-registration examples come from SPDK documentation; no transport benchmark was performed."
  ]
}