We were having a number of problems with the standard Fedora 2.6 nvme-cli utility on our
internal SPDK CIT testbeds, so we removed this RPM and installed the latest upstream
version from the master branch at https://github.com/linux-nvme/nvme-cli
. The latest
upstream version is 1.5, while the Fedora 2.6 RPM provides 1.3. This seems to have helped
with some of the problems we were seeing while running the nvmf/rdma tests on our SPDK CIT
However, we noticed https://github.com/spdk/nvme-cli
. This SPDK supported fork contains
a series of patches in the default spdk branch that are specific to spdk. See below.
These patches appear to be based on nvme-cli 1.3.
* What is the purpose of the spdk nvme-cli fork?
* Do we need these patches to run the SPDK CIT tests?
* Is there any plan to rebase this spdk branch and push these patches upstream to the
Here are the differences between the spdk branch and the nvme-cli master branch.
pick 5e9a978 nvme-cli: add SPDK support
pick dc50f8a spdk/nvme-cli: add the numa support for latest SPDK code
pick 12f27ea spdk/nvme-cli: add DPDK dependencies for DPDK v17.11
pick d366989 spdk/nvme-cli:Avoid spdk/nvme_cli compile failed with gcc -Werror option.
pick 06e35f9 nvme-cli/spdk: add a bdf check function for input device
pick 54624<tel:54624>af nvme-cli/spdk: handle IO commands with zero based blkcnt
pick 1dbe081 nvme-cli/spdk: support more NVMe-oF configuration
pick 38561<tel:38561>cc nvme-cli/spdk: only add -I to CFLAGS
pick 8a382fe nvme-cli/spdk: add SPDK libs via LDFLAGS
pick a674f70 nvme-cli/spdk: simplify linker options using -L
pick e953293 nvme-cli/spdk: allow building with sanitizers
pick 479c515 nvme-cli: fix possible string truncation
pick 83a0556 nvme-cli/spdk: fix build with coverage enabled
pick 2308379<tel:2308379> nvme-cli/spdk: fix link order of DPDK dependencies
pick 7196<tel:7196>cd4 spdk/nvme-cli: update with the new spdk_nvme_connect() API
pick 2761<tel:2761>b5d nvme-cli/spdk: add the support for the Intel plugin
pick db1d66f nvme-cli/spdk: add the support for the show-regs command
# Rebase 5bc6f64..c78cc41 onto 5bc6f64 (17 commands)