NVME-SNDK-GET-LAT(1)
π NVME-SNDK-GET-LAT(1) β ok bestie, this one's from the NVMe Manual
Hey so real talk, this page is nvme-sndk-get-latency-monitor-log(1) and it's here to make the latency monitor log page data actually, like, readable to humans. Slay.
β¨ NAME β¨
nvme-sndk-get-latency-monitor-log β display latency monitor log page data in human readable format π«Ά
πΈ SYNOPSIS πΈ
nvme [<global-options>] sndk get-latency-monitor-log <device>
π¦ DESCRIPTION π¦
So for the NVMe device you hand it, it's gonna give you the latency monitor log page data. That's the whole vibe.
The <device> parameter is a mandatory NVMe character device β like /dev/nvme0, yk how it is.
β οΈ Heads up bestie: this will only work on Sandisk devices that support this log page. Results for any other device are undefined β like genuinely undefined, not "probably fine" undefined. Don't play with it. π
On success it returns 0, and an error code otherwise. Periodt.
π OPTIONS π
π GLOBAL OPTIONS
These ones live at the top-level nvme command, and they're all available to this subcommand too. Iykyk.
--dry-runβ prints the command it would run, but doesn't actually run it. All the aesthetic, none of the consequences β¨--no-ioctl-probingβ turns off probing for 64-bit IOCTL support.--no-retriesβ kills the retry logic on transient errors. One shot, no do-overs π₯-o <fmt>,--output-format=<fmt>β sets the reporting format tonormal,tabular,'json, orbinary. Only one output format at a time, pick a lane bestie π--output-format-version=<version>β picks the output format version. Version1uses the original field naming, while version2(the default, highkey) gives you more consistent and script-friendly field names. Any other version gets rejected, no cap.--quietβ suppresses informational messages. Errors are still reported tho, and--quietcancels out any--verbosefor the library log level. They literally cancel each other out π«Ά--set-options=<key=value>[,<key=value>...]β sets libnvme library options for this invocation. The supported keys areforce-4k,mi-probe-enabled,test-base-dirandtest-sysfs-dir.--timeout=<ms>β sets the command timeout in milliseconds.infiniteor-1waits with no time limit (0xffffffff). She can wait forever if you want her to π-v,--verboseβ turns up the detail in the output. You can pass it multiple times to go even more verbose. Obsessed with the escalation ngl.
These options can also be set as machine-wide defaults in nvme-cli.conf(5). And a command-line flag always overrides the file β CLI stays the main character π
π EXAMPLES π
- Displays the get latency monitor log for the device:
# nvme sndk get-latency-monitor-log /dev/nvme0
π NVME π
Part of the nvme-user suite. She's got a whole family, iconic.
π that's the whole page, bestie β go get those latency numbers π
mwah π β brought to you by the NVMe crew, version dated 10/30/2026, so go forth and monitor those latencies responsibly π
π¦ where this page comes from
- arch rolling: nvme-cli 3.2-1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms