Install xnvme with Homebrew, apk, dnf

Project links

• Homepage
• Repository
• Package manager page

Commands and aliases

• kvs
• lblk
• xdd
• xnvme
• xnvme-driver
• xnvme_file
• zoned

Project history

The GitHub repository was created in April 2020. The documentation presents libxnvme as the foundation: it provides memory-management helpers, synchronous and asynchronous NVMe command submission, convenience functions, command-line tools, and backend retargeting over drivers such as Linux IOCTL, libaio, io_uring, SPDK, FreeBSD IOCTL, and others.

The project's research framing was published in the 2022 paper 'I/O interface independence with xNVMe', which argues that modern storage programmers face too many idiosyncratic high-performance I/O interfaces and presents xNVMe as a thin abstraction over those choices.

Adoption history

xNVMe adoption is strongest in storage systems, benchmarking, and research workflows rather than general desktop use. The official docs include tools such as xnvme, lblk, zoned, xdd, xnvmeperf, and a fio I/O engine, which makes the package useful both as a library and as a command-line toolbox for NVMe experiments.

The integration story is important. SPDK documents an xNVMe bdev module that can issue I/O through mechanisms such as libaio, io_uring, asynchronous IOCTL with io_uring passthrough, POSIX aio, and emulated aio, while fio documents an xnvme engine for accessing NVMe devices through xNVMe's C API and backend choices.

How it is used

Developers use libxnvme when they need to allocate suitable buffers, submit NVMe commands, choose synchronous or asynchronous completion models, and switch between backend implementations without rewriting the application for every platform or driver stack.

Operators and researchers use the packaged tools for direct device experiments: querying devices, issuing commands, working with logical blocks and zoned namespaces, exercising xdd-style data movement, and running fio jobs through the xnvme engine.

Why package nerds care

xNVMe is significant because it packages a hard systems-programming problem as installable infrastructure. It does not hide NVMe; it standardizes the messy edge between applications, kernel APIs, userspace drivers, DMA-safe buffers, and benchmark tools.

For package nerds, it is also a marker of modern storage packaging: a formula can ship a library plus multiple expert CLIs, and those binaries matter to developers working on databases, file systems, benchmarks, zoned storage, and SPDK/io_uring experiments.

Timeline

• 2020-04-02: The xnvme/xnvme GitHub repository is created.
• 2022: 'I/O interface independence with xNVMe' is published, documenting the project's design and performance motivation.
• 2022-2024: GitHub releases show the public 0.x line maturing through storage tools, documentation, and backend work.
• 2020s: xNVMe appears in SPDK and fio documentation as a backend/engine for NVMe I/O across multiple mechanisms.

Related projects

• SPDK is a key adjacent userspace storage stack; its bdev_xnvme module uses xNVMe as an I/O mechanism abstraction.
• fio includes an xnvme I/O engine for benchmarking NVMe devices through xNVMe.
• io_uring, libaio, NVMe IOCTLs, and SPDK drivers are backend paths xNVMe helps applications target.
• nvme-cli is an adjacent command-line NVMe administration tool, while xNVMe focuses on programmable I/O and backend independence.

Sources

• https://api.github.com/repos/xnvme/xnvme
• https://dl.acm.org/doi/10.1145/3534056.3534936
• https://fio.readthedocs.io/en/latest/fio_doc.html
• https://github.com/xnvme/xnvme
• https://xnvme.io/
• https://xnvme.io/tools/fio/index.html
• https://xnvme.io/tutorial/bdev_xnvme/index.html