NVME-FEAT-POWER-M(1)

πŸ“¦ version 3.2, in arch rolling

πŸ’… NVME-FEAT-POWER-M(1) β€” nvme-feat-power-mgmt

okay so bestie, welcome to the NVMe Manual page for nvme-feat-power-mgmt, and no cap, this is the one that gets and sets your power management feature. let's go πŸ’–


✨ NAME ✨

nvme-feat-power-mgmt β€” get and set power management feature πŸŽ€

πŸ¦‹ SYNOPSIS πŸ¦‹

nvme [<global-options>] feat power-mgmt <device>
                        [--ps=<ps> | -p <ps>] [--wh=<wh> | -w <wh>]
                        [--sel=<select> | -S <select>] [--save | -s]

🌸 DESCRIPTION 🌸

Get and set power management feature. that's the whole vibe, like literally both directions in one little command πŸ‘‘

The <device> parameter is mandatory β€” it's not optional, it's not a suggestion, it is the moment. and it can be either of these:

  • the NVMe character device (ex: /dev/nvme0), or
  • a namespace block device (ex: /dev/nvme0n1)

so if you pass the setting option (--ps), the command will update the power management configuration. if you omit --ps, it will retrieve and display the current configuration instead. one flag decides which whole personality it's giving 😌

On success it returns 0, error code otherwise. periodt.

πŸ’… OPTIONS πŸ’…

  • -p <ps>, --ps=<ps> β€” Power state. this is where you specify the power state to transition the controller to 🧚
  • -w <wh>, --wh=<wh> β€” Workload hint. it provides a hint to the controller about the workload characteristics, like a little heads-up so it knows what's coming πŸ”₯
  • -S <select>, --sel=<select> β€” Select (SEL): this field specifies which value of the attributes to return in the provided data. the iconic lineup:
    • 0 β€” current β€” Current
    • 1 β€” default β€” Default
    • 2 β€” saved β€” Saved
    • 3 β€” supported β€” Supported capabilities
  • -s, --save β€” Save the attribute so that it persists through all power states and resets. the "make it stick" button, we love her πŸ’–

🌈 GLOBAL OPTIONS 🌈

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

  • --dry-run β€” Print the command that would be executed, but do not actually execute it. manifesting the command without committing to it πŸ™ˆ
  • --no-ioctl-probing β€” Disable probing for 64-bit IOCTL support.
  • --no-retries β€” Disable retry logic on transient errors. one shot, no do-overs πŸ’€
  • -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 your fighter, not all four ⭐
  • --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. she's silencing the group chat but still reading the important texts 😭
  • --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). she'll wait forever, lowkey devoted πŸ•°οΈ
  • -v, --verbose β€” Increase the level of detail in the output. May be specified multiple times to further increase verbosity. stack her like accessories πŸ’œ
these options can also be set as machine-wide defaults in nvme-cli.conf(5). A command-line flag always overrides the file. no cap, the flag wins every time πŸ‘‘

πŸ“ EXAMPLES πŸ“

  • Has the program issue a feat power-mgmt to get the current configuration:
# nvme feat power-mgmt /dev/nvme0
  • Has the program issue a feat power-mgmt to set power state and workload hint:
# nvme feat power-mgmt /dev/nvme0 --ps=1 --wh=2 --save

πŸ‘‘ NVME πŸ‘‘

Part of the nvme-user suite. icons only, fr fr 🌟


and that's the page, bestie πŸŽ€ huge thank you to the NVMe crew for this one β€” this copy is dated 10/30/2026, so go slay some power states and remember: --save it or lose it πŸ’–βœ¨

πŸ“¦ where this page comes from