NVME-OCP-GET-LATE(1)

📦 version 3.2, in arch rolling

💅 NVME-OCP-GET-LATENCY-MONITOR 💅

okay so bestie, welcome to the NVMe Manual section for this one, and buckle up because we're reading a get-latency-monitor value and printing it like the icon we are. ✨

🌸 NAME 🌸

nvme-ocp-get-latency-monitor — define and print get-latency-monitor value. that's the whole vibe, that's the assignment. 💖

🦋 SYNOPSIS 🦋

nvme [<global-options>] ocp get-latency-monitor <device>
                        [--sel=<select> | -s <select>]
                        [--namespace-id <nsid> | -n <nsid>]
                        [--no-uuid | -u]

like, look at her. main character energy in four lines. no cap. 👑

🎀 DESCRIPTION 🎀

so the <device> parameter is mandatory, bestie — you literally cannot skip it, it's not one of those optional besties that ghosts you. and it can be either the NVMe character device (ex: /dev/nvme0) or a block device (ex: /dev/nvme0n1). pick your fighter. 🫶

this will only work on OCP compliant devices that support this feature. results for any other device are undefined — and we do not fw undefined behavior in this house, that's giving chaos demon energy. 💀

on success it returns 0, error code otherwise. simple as that, periodt.

✨ OPTIONS ✨

  • -n <nsid>, --namespace-id=<nsid> — NSID: assign the different kind of nsid value (like active, inactive and invalid nsids) and check the get feature command response. and the broadcast value 0xffffffff can also be given as all or -1. yes, three whole ways to say the same thing, she contains multitudes. 🌈
  • -s <select>, --sel=<select> — Select (SEL): this field specifies which value of the attributes to return in the provided data. here's the tea, laid out on a little platter for you:
    • 0 → current → Current
    • 1 → default → Default
    • 2 → saved → Saved
    • 3 → supported → Supported capabilities

literally the whole menu. choose wisely. 🍓

  • -u, --no-uuid — do not try to automatically detect UUID index for this command (required for old OCP 1.0 support). she's for the legacy girlies, respect her. 🙈

⭐ GLOBAL OPTIONS ⭐

these are defined at the top-level nvme command and are available to this subcommand too, so they're like the group chat everyone gets added to:

  • --dry-run — print the command that would be executed, but do not actually execute it. all talk, no action, honestly relatable. 💅
  • --no-ioctl-probing — disable probing for 64-bit IOCTL support.
  • --no-retries — disable retry logic on transient errors. one shot, no second chances.
  • -o <fmt>, --output-format=<fmt> — set the reporting format to normal, tabular, 'json, or binary. only one output format may be used at a time. no, you cannot have two, i know you want two. 😭
  • --output-format-version=<version> — select the output format version. Version 1 uses the original field naming, while version 2 (default) provides more consistent and script-friendly field names. other versions are rejected — firmly, politely, rejected. 🚫
  • --quiet — suppress informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. she's not being rude, she's just not doing small talk.
  • --set-options=<key=value>[,<key=value>...] — set libnvme library options for this invocation. supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. mix and match, it's a build-your-own-adventure. 🧚
  • --timeout=<ms> — set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). she'll wait forever, that's devotion. 💜
  • -v, --verbose — increase the level of detail in the output. may be specified multiple times to further increase verbosity. stack it, layer it, go feral with it. 🔥
these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file. so if the file says one thing and your flag says another — the flag wins, every single time. no negotiation. 👑

💖 EXAMPLES 💖

  • has the program issue a get-latency-monitor to retrieve the 0xC5 get features. she's doing exactly what she says on the tin:
# nvme ocp get-latency-monitor /dev/nvme0

like... that's it. that's the whole ritual. iconic. ✨

🌟 NVME 🌟

part of the nvme-user suite. you're in good company, bestie. 🫶

aaaaand that's a wrap! 🎉 this lil page is from the NVMe manual, dated 10/30/2026 — go forth and monitor those latencies, you absolute legend. iykyk. 💅💖🌸

📦 where this page comes from