NVME-SNDK-VS-PCIE(1)

📦
version 3.2 · 9 versions
, in arch rolling

💅 NVME-SNDK-VS-PCIE(1) — the nvme manual, bestie edition ✨

Okay so this is the page for nvme-sndk-vs-pcie-stats, and yes that name is a mouthful but we move 💖 it lives inside the nvme manual.

🌸 NAME 🌸

nvme-sndk-vs-pcie-stats — it sends the NVMe sndk vs-pcie-stats command and hands you back the result. That's it. That's the whole gig 🎀

🦋 SYNOPSIS 🦋

nvme [<global-options>] sndk vs-pcie-stats <device>

That's the whole vibe. Globals in brackets (optional, slay), the subcommand, then a device you must give it 💅

👑 DESCRIPTION 👑

So for the NVMe device you hand it, it sends the super-special unique sndk vs-pcie-stats command and returns the PCIe statistics data. She's giving telemetry, she's giving intel 🌈

The <device> parameter is mandatory — no device, no party — and it can be either the NVMe character device (ex: /dev/nvme0) or... yeah, that's the example, use it wisely 🫶

⚠️ Heads up bestie: this only works on Sandisk devices that support this feature. Results for any other device are undefined — like, not "a little weird," actually undefined 💀 don't come for me if you try it on something else.

On success it returns 0; otherwise you get an error code. Exit status is giving pass/fail realness ✨

🎀 OPTIONS 🎀

💜 GLOBAL OPTIONS

These ones are defined up at the top-level nvme command, and your girl the subcommand gets to use them too:

  • --dry-run — prints the command it would execute, but doesn't actually execute it. All the rehearsal, none of the commitment 🙈
  • --no-ioctl-probing — disables probing for 64-bit IOCTL support. Just, like, don't check 🔥
  • --no-retries — kills the retry logic on transient errors. One shot, one opportunity 😭
  • -o <fmt>, --output-format=<fmt> — sets the reporting format to normal, tabular, json, or binary. Only one output format at a time, bestie, we don't do multitasking here 💅
  • --output-format-version=<version> — picks the output format version. Version 1 uses the original field naming, while version 2 (the default) gives you more consistent, script-friendly field names. Other versions are rejected — don't even try it 🚫
  • --quiet — suppresses informational messages. Errors still get reported, and --quiet cancels any --verbose for the library log level. Mutual destruction, iconic 💀
  • --set-options=<key=value>[,<key=value>...] — sets libnvme library options for this invocation. The supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. Mix and match, comma-separated, go off ✨
  • --timeout=<ms> — sets the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). Patience is a virtue, or whatever 🧚
  • -v, --verbose — increases the level of detail in the output. You can specify it multiple times to crank the verbosity even further. Spam that -v, she loves it 📈

These options can also be set as machine-wide defaults in nvme-cli.conf(5). A command-line flag always overrides the file — command line stays winning 👑

🌟 EXAMPLES 🌟

  • Has the program issue the sndk vs-pcie-stats command:
# nvme sndk vs-pcie-stats /dev/nvme0

Look at her go 🥹

⭐ NVME ⭐

Part of the nvme-user suite. Family reunion, everyone's invited 🫶

And that's the page, bestie! Written by the NVMe crew, dated 10/30/2026, from the NVMe manual source — go forth and read your PCIe stats responsibly 💜✨🎀

📦 where this page comes from