NVME-FEAT-INT-COA(1)

πŸ“¦ version 3.2, in arch rolling

πŸ’… NVME-FEAT-INT-COA(1) β€” nvme-feat-int-coalesce, bestie edition πŸ’…

okay so this is a page from the NVMe Manual, and it's literally about one of my fave little nvme subcommands: nvme-feat-int-coalesce. sit down, grab a strawberry drink πŸ“, and let's get into it.


✨ NAME ✨

nvme-feat-int-coalesce β€” get and set the interrupt coalescing feature πŸŽ€


🌸 SYNOPSIS 🌸

nvme [<global-options>] feat int-coalesce <device>
                        [--thr=<thr> | -t <thr>] [--time=<time> | -T <time>]
                        [--sel=<select> | -S <select>] [--save | -s]

πŸ¦‹ DESCRIPTION πŸ¦‹

Get and set the interrupt coalescing feature. that's the whole vibe, no cap.

The <device> parameter is mandatory β€” like, you cannot skip it, it's giving main character energy and it will not be ignored. it may be either the NVMe character device (ex: /dev/nvme0), or a namespace block device (ex: /dev/nvme0n1).

so here's the tea β˜•: if any of the setting options (--thr or --time) are specified, the command will update the interrupt coalescing configuration. but if none of these options are specified, it will just retrieve and display the current configuration β€” a little read-only moment, we love a low-stakes vibe check.

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


πŸ’– OPTIONS πŸ’–

  • -t <thr>, --thr=<thr> β€” Aggregation Threshold. specifies the minimum number of completion queue entries required to trigger an interrupt. like, it's the "how many before we yell" number πŸ”₯
  • -T <time>, --time=<time> β€” Aggregation Time. specifies the maximum time in 100 microsecond units that the controller may delay an interrupt due to coalescing. yes, 100 microsecond units, not regular microseconds, read it carefully bestie πŸ™ˆ
  • -S <select>, --sel=<select> β€” Select (SEL): this field specifies which value of the attributes to return in the provided data. here's the menu πŸ‘‘:
    • 0 β€” Name: current β€” Description: Current
    • 1 β€” Name: default β€” Description: Default
    • 2 β€” Name: saved β€” Description: Saved
    • 3 β€” Name: supported β€” Description: Supported capabilities
  • -s, --save β€” Save the attribute so that it persists through all power states and resets. it's giving commitment issues solved πŸ’€βœ¨

πŸ‘‘ GLOBAL OPTIONS πŸ‘‘

these are defined at the top-level nvme command and are available to this subcommand too, iykyk:

  • --dry-run β€” Print the command that would be executed, but do not actually execute it. rehearse the slay, don't perform it 🎭
  • --no-ioctl-probing β€” Disable probing for 64-bit IOCTL support.
  • --no-retries β€” Disable retry logic on transient errors.
  • -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. (yes, that quote mark before json is exactly how it's written in the original β€” not me, not my fault 🫢)
  • --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 β€” no negotiating with the bouncer πŸ’…
  • --quiet β€” Suppress informational messages. Errors are still reported, and --quiet cancels any --verbose for the library log level. shhh 🀫
  • --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). immovable object energy ⭐
  • -v, --verbose β€” Increase the level of detail in the output. May be specified multiple times to further increase verbosity. say it again, and again, and again πŸ—£οΈ
these options can also be set as machine-wide defaults in nvme-cli.conf(5). A command-line flag always overrides the file. the flag is the main character, the file is the supporting cast 🌈

🧚 EXAMPLES 🧚

  1. Has the program issue a feat int-coalesce to get the current configuration β€” just a lil peek πŸ‘€:
# nvme feat int-coalesce /dev/nvme0
  1. Has the program issue a feat int-coalesce to set the aggregation threshold and time β€” now we're actually changing things πŸ”₯:
# nvme feat int-coalesce /dev/nvme0 --thr=10 --time=5 --save

πŸ’œ NVME πŸ’œ

Part of the nvme-user suite. iconic, honestly.


and that's the whole page, bestie πŸ’–βœ¨πŸŽ€πŸ¦‹πŸŒΈπŸ’…πŸ«Ά β€” with love from the NVMe fam, dated 10/30/2026. go forth and coalesce those interrupts responsibly. bye!! πŸ˜­πŸ‘‘β­

πŸ“¦ where this page comes from