NVME-FEAT-POWER-L(1)

📦 version 3.2, in arch rolling

✨ nvme-feat-power-l(1) — the NVMe Manual, but make it a group chat ✨

okay bestie, sit down, hydrate, and let me tell you about nvme-feat-power-l from the NVMe Manual. it's a little subcommand that gets and sets the power limit feature on your drive, and honestly? it's giving main character energy for such a tiny command. 💅

🌸 NAME 🌸

nvme-feat-power-l — get and set the power limit feature. that's it, that's the whole vibe. get it, set it, slay. ✨

🦋 SYNOPSIS 🦋

nvme [<global-options>] feat power-limit <device>
                        [--pwrlm=<pwrlm> | -p <pwrlm>] [--pvlmt=<pvlmt> | -t <pvlmt>]
                        [--sel=<select> | -S <select>] [--save | -s]

like, look at her. she's got a <device>, she's got options, she's got short flags and long flags, because she's flexible like that. 🎀

💖 DESCRIPTION 💖

okay so: get and set power limit feature. that's the whole assignment. 🫶

the <device> parameter is mandatory — you literally cannot skip it, no cap — and it can be either:

  • an NVMe character device, like /dev/nvme0
  • or a namespace block device, like /dev/nvme0n1

either one is fine, she's not picky 💜

here's the behaviour check, listen up:

  • if any of the setting options (--pwrlm or --pvlmt) are specified, the command will update the power limit configuration.
  • if none of these options are specified, it will retrieve and display the current configuration. read-only era. 🌈

and on success, it returns 0. on anything else — error code. bye. 😭

🎀 OPTIONS 🎀

  • -p <pwrlm>, --pwrlm=<pwrlm> — Power Limit. specifies the power limit value to be applied to the controller. this is you telling the drive "bestie, this is your limit." 🔥
  • -t <pvlmt>, --pvlmt=<pvlmt> — Power Limit Type. specifies the type of power limit — like, e.g., static or dynamic limit. yes there's a type, no you cannot ignore it. 💅
  • -S <select>, --sel=<select> — Select (SEL). this field specifies which value of the attributes to return in the provided data. the vibes are as follows:
    • 0 — current — Current ✨
    • 1 — default — Default 🎀
    • 2 — saved — Saved 💾
    • 3 — supported — Supported capabilities 👑

(that's literally the exact table, just laid out flat so it fits your terminal, iykyk 🦋)

  • -s, --save — save the attribute so that it persists through all power states and resets. she stays. she's permanent. periodt. 👑

⭐ GLOBAL OPTIONS ⭐

these are defined at the top-level nvme command, but they're available to this subcommand too — shared custody, we love to see it 🫶

  • --dry-run — print the command that would be executed, but do not actually execute it. window shopping, essentially 🙈
  • --no-ioctl-probing — disable probing for 64-bit IOCTL support. no poking around 🔍
  • --no-retries — disable retry logic on transient errors. one shot, one opportunity 💀
  • -o <fmt>, --output-format=<fmt> — set the reporting format to normal, tabular, 'json, or binary. (yes that's exactly how it's written in the original — the quote is part of the deal, don't come for me 😭) only one output format may be used at a time.
  • --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 — she does not entertain them 🚫
  • --quiet — suppress informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. 🤫
  • --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. very "customize your experience" of it 🎀
  • --timeout=<ms> — set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). forever girlies rise 🌸
  • -v, --verbose — increase the level of detail in the output. may be specified multiple times to further increase verbosity. stack it. go off. 🔥
💡 these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file. file says one thing, flag says another, flag wins, no debate. 💅

🌈 EXAMPLES 🌈

  1. has the program issue a feat power-limit to get the current configuration:
# nvme feat power-limit /dev/nvme0

look at her go. no flags, just vibes, just reading. 🦋

  1. has the program issue a feat power-limit to set power limit with saving enabled:
# nvme feat power-limit /dev/nvme0 --pwrlm=25 --pvlmt=1 --save

now this is main character energy — limit set, type set, save flag on. iconic. 🎀

👑 NVME 👑

part of the nvme-user suite. you're in the family now, bestie 🫶

and that's the whole page, no notes. this gem is from the NVMe manual, dated 10/30/2026, part of the nvme-user suite — go forth and power-limit responsibly, love you, bye! 💖✨🎀🦋

📦 where this page comes from