NVM-Express user space tooling for Linux.
nvme-cli uses meson as build system. In order to build nvme-cli run following commands
$ meson .build
$ ninja -C .build
nvme-cli depends on zlib and json-c
To install, run:
# meson install -C .build
There is a Makefile wrapper for meson for backwards compatiblily
$ make
# make install
RPM build support via Makefile that uses meson
$ make rpm
If not sure how to use, find the top-level documentation with:
$ man nvme
Or find a short summary with:
$ nvme help
nvme-cli is tested on Alpine Linux 3.3. Install it using:
# apk update && apk add nvme-cli nvme-cli-doc
if you just use the device you're after, it will work flawless.
# nvme smart-log /dev/nvme0
Smart Log for NVME device:/dev/nvme0 namespace-id:ffffffff
critical_warning : 0
temperature : 49 C
available_spare : 100%
nvme-cli is available in the [community] repository. It can be installed with:
# pacman -S nvme-cli
The development version can be installed from AUR, e.g.:
$ yay -S nvme-cli-git
nvme-cli is available in Debian 9 and up. Install it with your favorite package manager. For example:
$ sudo apt install nvme-cli
nvme-cli is available in Fedora 23 and up. Install it with your favorite package manager. For example:
$ sudo dnf install nvme-cli
nvme-cli is available in the FreeBSD Ports Collection. A prebuilt binary
package can be installed with:
# pkg install nvme-clinvme-cli is available and tested in portage:
$ emerge -av nvme-cli
The attribute is named nvme-cli and can e.g. be installed with:
$ nix-env -f '<nixpkgs>' -iA nvme-cli
nvme-cli is available in openSUSE Leap 42.2 or later and Tumbleweed. You can install it using zypper. For example:
$ sudo zypper install nvme-cli
nvme-cli is supported in the Universe package sources for many architectures. For a complete list try running:
rmadison nvme-cli
nvme-cli | 0.5-1 | xenial/universe | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
nvme-cli | 0.5-1ubuntu0.2 | xenial-updates/universe | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
nvme-cli | 1.5-1 | bionic/universe | source, amd64, arm64, armhf, i386, ppc64el, s390x
nvme-cli | 1.5-1ubuntu1.2 | bionic-updates | source, amd64, arm64, armhf, i386, ppc64el, s390x
nvme-cli | 1.9-1 | focal/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x
nvme-cli | 1.9-1ubuntu0.1 | focal-updates | source, amd64, arm64, armhf, ppc64el, riscv64, s390x
nvme-cli | 1.14-1 | impish | source, amd64, arm64, armhf, ppc64el, riscv64, s390x
nvme-cli | 1.16-3 | jammy | source, amd64, arm64, armhf, ppc64el, riscv64, s390x
A Debian based package for nvme-cli is currently maintained as a Ubuntu PPA. To install nvme-cli using this approach please perform the following steps:
- Perform an update of your repository list:
sudo apt-get update
- Get nvme-cli!
sudo apt-get install nvme-cli
- Test the code.
sudo nvme list
In the case of no NVMe devices you will see
No NVMe devices detected.
otherwise you will see information about each NVMe device installed in the system.
An nvme-cli recipe
is available as part of the meta-openembeded layer collection.
nvme-cli is available as buildroot package. The
package is named nvme.
TBD
You may wish to add a new command or possibly an entirely new plug-in for some special extension outside the spec.
This project provides macros that help generate the code for you. If you're interested in how that works, it is very similar to how trace events are created by Linux kernel's 'ftrace' component.
The first thing to do is define a new command entry in the command list. This is declared in nvme-builtin.h. Simply append a new "ENTRY" into the list. The ENTRY normally takes three arguments: the "name" of the subcommand (this is what the user will type at the command line to invoke your command), a short help description of what your command does, and the name of the function callback that you're going to write. Additionally, You can declare an alias name of subcommand with fourth argument, if needed.
After the ENTRY is defined, you need to implement the callback. It takes four arguments: argc, argv, the command structure associated with the callback, and the plug-in structure that contains that command. The prototype looks like this:
int f(int argc, char **argv, struct command *cmd, struct plugin *plugin);The argc and argv are adjusted from the command line arguments to start after the sub-command. So if the command line is "nvme foo --option=bar", the argc is 1 and argv starts at "--option".
You can then define argument parsing for your sub-command's specific options then do some command specific action in your callback.
The nvme-cli provides macros to make define a new plug-in simpler. You can certainly do all this by hand if you want, but it should be easier to get going using the macros. To start, first create a header file to define your plugin. This is where you will give your plugin a name, description, and define all the sub-commands your plugin implements.
There is a very important order on how to define the plugin. The following is a basic example on how to start this:
File: foo-plugin.h
#undef CMD_INC_FILE
#define CMD_INC_FILE plugins/foo/foo-plugin
#if !defined(FOO) || defined(CMD_HEADER_MULTI_READ)
#define FOO
#include "cmd.h"
PLUGIN(NAME("foo", "Foo plugin"),
COMMAND_LIST(
ENTRY("bar", "foo bar", bar)
ENTRY("baz", "foo baz", baz)
ENTRY("qux", "foo quz", qux)
)
);
#endif
#include "define_cmd.h"In order to have the compiler generate the plugin through the xmacro expansion, you need to include this header in your source file, with pre-defining macro directive to create the commands.
To get started from the above example, we just need to define "CREATE_CMD" and include the header:
File: foo-plugin.c
#include "nvme.h"
#define CREATE_CMD
#include "foo-plugin.h"After that, you just need to implement the functions you defined in each ENTRY, then append the object file name to the meson.build "sources".
In case meson doesn't find libnvme header files (via pkg-config) it will fallback using subprojects. meson checks out libnvme in subprojects directory as git tree once to the commit level specified in the libnvme.wrap file revision parm. After this initial checkout, the libnvme code level will not change unless explicitly told. That means if the current branch is updated via git, the subprojects/libnvme branch will not updated accordingly. To update it, either use the normal git operations or the command:
$ meson subprojects update
libnvme depends on the /sys/class/nvme-subsystem interface which was introduced in the Linux kernel release v4.15. Hence nvme-cli 2.x is only working on kernels >= v4.15. For older kernels nvme-cli 1.x is recommended to be used.
There are two ways to send code changes to the project. The first one is by sending the changes to [email protected]. The second one is by posting a pull request on github. In both cases please follow the Linux contributions guidelines as documented in
https://docs.kernel.org/process/submitting-patches.html#
That means the changes should be a clean series (no merges should be present in a github PR for example) and every commit should build.
See also https://opensource.com/article/19/7/create-pull-request-github
This example here assumes, the changes are in a branch called fix-something, which branched away from master in the past. In the meantime the upstream project has changed, hence the fix-something branch is not based on the current HEAD. Before posting the PR, the branch should be rebased on the current HEAD and retest everything.
For example rebasing can be done by following steps
# Update master branch
# upstream == https://github.com/linux-nvme/nvme-cli.git
$ git switch master
$ git fetch --all
$ git reset --hard upstream/master
# Make sure all dependencies are up to date and make a sanity build
$ meson subprojects update
$ ninja -C .build
# Go back to the fix-something branch
$ git switch fix-something
# Rebase it to the current HEAD
$ git rebase master
[fixup all merge conflicts]
[retest]
# Push your changes to github and trigger a PR
$ git push -u origin fix-something
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent