NVME-WDC-SET-LATE(1)

💅 nvme-wdc-set-latency-monitor-feature(1) — the NVMe Manual, but make it make sense

okay bestie, gather round, because this one is a NVMe Manual page about a WDC (Western Digital) vendor command, and it's genuinely not that deep once we break it down. this whole page is nvme-wdc-set-latency-monitor-feature — yes, that's the full name, it's giving "my parents let me pick my own name" energy 🎀 — and it lives in the nvme command family as a subcommand.

---

✨ NAME ✨

nvme-wdc-set-latency-monitor-feature — Set NVMe WDC latency monitor feature options. that's the whole vibe: you're flipping knobs on the latency monitor. 💅

---

🦋 SYNOPSIS 🦋

nvme [<global-options>] wdc set-latency-monitor-feature <device>
                        [--active_bucket_timer_threshold=<NUM> | -t <NUM>]
                        [--active_threshold_a=<NUM> | -a <NUM>]
                        [--active_threshold_b=<NUM> | -b <NUM>]
                        [--active_threshold_c=<NUM> | -c <NUM>]
                        [--active_threshold_d=<NUM> | -d <NUM>]
                        [--active_latency_config=<NUM> | -f <NUM>]
                        [--active_latency_minimum_window=<NUM> | -w <NUM>]
                        [--debug_log_trigger_enable=<NUM> | -r <NUM>]
                        [--discard_debug_log=<NUM> | -l <NUM>]
                        [--latency_monitor_feature_enable=<NUM> | -e <NUM>]

like, yes, that's a lot of brackets. it's an options buffet, take what you need. 🍓

---

🌸 DESCRIPTION 🌸

for the NVMe device you hand it, this command sets the latency monitor feature options — if the device supports it. no cap, that "if supported by the device" part is doing real work, so don't come for me if your drive says no. 🙈

the <device> parameter is mandatory and it wants an NVMe character device, ex: /dev/nvme0.

you can check how your setting landed with the get-latency-monitor-log command. slay, feedback loop. 🔥

on success it returns 0, error code otherwise. classic.

---

💜 OPTIONS 💜

• -t <NUM>, --active_bucket_timer_threshold=<NUM> — the value that loads the Active Bucket Timer Threshold; default value is 07E0h.
• -a <NUM>, --active_threshold_a=<NUM> — the value that loads into the Active Threshold A; default value is 05h.
• -b <NUM>, --active_threshold_b=<NUM> — the value that loads into the Active Threshold B; default value is 13h.
• -c <NUM>, --active_threshold_c=<NUM> — the value that loads into the Active Threshold C; default value is 1Eh.
• -d <NUM>, --active_threshold_d=<NUM> — the value that loads into the Active Threshold D; default value is 2Eh.
• -f <NUM>, --active_latency_config=<NUM> — the value that loads into the Active Latency Configuration. this configures how both the Active Latency Stamp and the Active Measured Latency Fields get updated, on a per I/O command (Read, Write, Deallocate) counter basis; default value is 0FFFh. highkey the most extra option here.
• -w <NUM>, --active_latency_minimum_window=<NUM> — the value that loads into the Active Latency Minimum Window; default value is 0Ah.
• -r <NUM>, --debug_log_trigger_enable=<NUM> — the value that loads into the Debug Log Trigger Enable. when set to 1b, the first time the bucket/counter combination is incremented a debug log is triggered. when cleared to 0b a debug log will not be triggered when the bucket/counter combination is incremented. it's giving "one (1) shot".
• -l <NUM>, --discard_debug_log=<NUM> — Discard Debug Log. when cleared to 00h the debug log, if it exists, will not be cleared. when set to 01h the debug log will be discarded so another log can be triggered — and all the fields in the Set Features Data structure are valid. when set to 02h the debug log will be discarded so another log can be triggered — but none of the other fields of the Set Features Data structure are valid. little 02h plot twist for you 💀
• -e <NUM>, --latency_monitor_feature_enable=<NUM> — Latency Monitor Feature Enable. when set to 01h the Latency Monitor Feature is enabled. when cleared to 00h the Latency Monitor Feature is disabled. on/off, iconic, no notes. 👑

---

🌈 GLOBAL OPTIONS 🌈

bestie these live at the top-level nvme command, so they're available to this subcommand too. main character options, honestly:

• --dry-run — print the command that would be executed, but don't actually execute it. rehearsal era. 🎀
• --no-ioctl-probing — disable probing for 64-bit IOCTL support.
• --no-retries — disable retry logic on transient errors. yolo mode, but make it official.
• -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. pick one, babe.
• --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. 🫶
• --quiet — suppress informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. so you can't have both, it's a whole thing.
• --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.
• --timeout=<ms> — set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). patiently waiting forever, respectfully.
• -v, --verbose — increase the level of detail in the output. may be specified multiple times to further increase verbosity. spam it, honestly. ✨

also! these options can be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file. file says one thing, you say another, you win. periodt.

---

🧚 EXAMPLES 🧚

• Set NVMe WDC latency monitor feature options enabled with default value values:

# nvme wdc set-latency-monitor-feature /dev/nvme0 -e 1

• Set NVMe WDC latency monitor feature options disabled with default value values:

# nvme wdc set-latency-monitor-feature /dev/nvme0 -e 0

• Set NVMe WDC latency monitor feature options enabled with specific values:

# nvme wdc set-latency-monitor-feature /dev/nvme0 --active_bucket_timer_threshold=1 \
            --active_threshold_a=0x0 \
            --active_threshold_b=0x1 \
            --active_threshold_c=0x2 \
            --active_threshold_d=0x3 \
            --active_latency_config=0xfff \
            --active_latency_minimum_window=0 \
            --debug_log_trigger_enable=0 \
            --discard_debug_log=0 \
            --latency_monitor_feature_enable=0x1

look at that last one, all those continuations lined up like a little squad. obsessed. 😭💖

---

⭐ NVME ⭐

Part of the nvme-user suite. one big happy family.

---

and that's the whole page, bestie — no crumbs left behind 🦋✨

sign-off vibes: this was the NVMe manual, dated 10/30/2026, filing itself under NVME-WDC-SET-LATE(1) because apparently even manpages get nicknames. go forth and set some latency monitors, you absolute icon. 💅🌟