Simon A. F. Lund 27f73d5a45 fix(build): disable the upcie-cuda backend when nvcc is not found
With -Dwith-cuda=auto, a host with the CUDA runtime but no nvcc failed
to configure, since the upcie-cuda backend needs nvcc. The backend is
now disabled on such a host; -Dwith-cuda=enabled still requires nvcc.

Assisted-by: Claude Code:claude-opus-5-5
Signed-off-by: Simon A. F. Lund <os@safl.dk>
2026-11-16 18:18:32 +01:00
2024-09-11 13:56:13 +02:00

xNVMe Logo

xNVMe: cross-platform libraries and tools for NVMe devices

CI Coverity pre-commit REUSE status

See: https://xnvme.io/ for documentation

xNVMe provides APIs, libraries, and tools for user space programming of NVMe devices on Linux, FreeBSD, macOS, and Windows, through a single C API backed by the libxnvme library. The library carries backends utilizing and interfacing with the following, chosen at runtime, so the same application code runs unmodified across them:

  • Linux: io_uring, io_uring_cmd, libaio, block-layer IOCTLs
  • FreeBSD, macOS, Windows: the platform's native NVMe driver
  • SPDK, the popular user space NVMe driver on Linux and FreeBSD, for CPU-initiated I/O
  • uPCIe, a blazingly fast user space PCIe driver on Linux, with P2P data movement and support for CPU-initiated, Accelerator-assisted, and Accelerator-initiated I/O; currently compatible with CUDA and HIP (ROCm)

On top of libxnvme:

  • Command sets: libxnvme_nvm (NVM), libxnvme_znd (Zoned), libxnvme_kvs (KV)
  • xnvme, the command line; run it without arguments to see where to start
  • xnvme perf, synthetic workload generation with minimal overhead, to benchmark I/O processing at unprecedented efficiency across all of xNVMe's backends
  • xnvme homi, the software equivalent of SR-IOV: a daemon enabling multiple users, different processes on the host as well as compute kernels on accelerators, to run I/O directly against a single NVMe controller
  • xnvme qublk, a ublk-server implementation enabling kernel I/O and file systems to run in concert with the blazingly fast user space NVMe drivers

Contact and Contributions

xNVMe: is in active development and maintained by Simon A. F. Lund simon.lund@samsung.com, pull requests are most welcome. See, CONTRIBUTORS.md for a list of contributors to the current and previous versions of xNVMe. For a contributor-guidelines then have a look at the online documentation:

S
Description
No description provided
Readme BSD-3-Clause 35 MiB
Languages
C 70%
Python 22.6%
Meson 2%
Cuda 1.6%
Makefile 1.6%
Other 1.9%