XNVME-PIOC(1)

πŸ“¦ version 0.7.5, in alpine 3.24, epel 9, fedora 43, fedora 44

πŸ’– XNVME-PIOC(1) β€” the xnvme pioc page, bestie edition πŸ’–

okay so this is a page from the xNVMe manual, and it's literally about yeeting your own custom IO Command through the stack. group chat, gather round 🫢


✨ NAME ✨

xnvme-pioc β€” Pass a used-defined IO Command through

(yes bestie, "used-defined" is what the original says, i am not touching it, it's iconic and i refuse πŸ™ˆ)


🌸 SYNOPSIS 🌸

xnvme pioc <uri> [<args>]

πŸ¦‹ DESCRIPTION πŸ¦‹

Pass a used-defined IO Command through.

that's the whole description. short, sweet, main character energy. πŸ’…


πŸ‘‘ REQUIRED πŸ‘‘

you gotta give it this one, no skipping:

  • <uri> β€” the Device URI. examples given: '/dev/nvme0n1', '0000:01:00.1', '10.9.8.1.8888', '\.PhysicalDrive1'

⭐ OPTIONAL ⭐

all the little knobs and dials, no cap:

  • --cdw0 0xNUM β€” Command Dword0
  • --cdw1 0xNUM β€” Command Dword1
  • --cdw2 0xNUM β€” Command Dword2
  • --cdw3 0xNUM β€” Command Dword3
  • --cdw4 0xNUM β€” Command Dword4
  • --cdw4 0xNUM β€” Command Dword4
  • --cdw5 0xNUM β€” Command Dword5
  • --cdw6 0xNUM β€” Command Dword6
  • --cdw7 0xNUM β€” Command Dword7
  • --cdw8 0xNUM β€” Command Dword8
  • --cdw9 0xNUM β€” Command Dword9
  • --cdw10 0xNUM β€” Command Dword10
  • --cdw11 0xNUM β€” Command Dword11
  • --cdw12 0xNUM β€” Command Dword12
  • --cdw13 0xNUM β€” Command Dword13
  • --cdw14 0xNUM β€” Command Dword14
  • --cdw15 0xNUM β€” Command Dword15
  • --opcode 0xNUM β€” Command opcode
  • --nsid 0xNUM β€” Namespace Identifier for Command Construction
  • --data-input FILE β€” Path to data input-file
  • --data-output FILE β€” Path to data output-file
  • --data-nbytes NUM β€” Data size in bytes
  • --meta-input FILE β€” Path to meta input-file
  • --meta-output FILE β€” Path to meta output-file
  • --meta-nbytes NUM β€” Meta size in bytes
  • --verbose β€” Increase output info
  • --subnqn STRING β€” Subsystem NQN of the NVMe over Fabrics endpoint e.g. 'nqn.2022-06.io.xnvme:ctrlnode1'
  • --hostnqn STRING β€” The host NQN to use when connecting to NVMe over Fabrics controllers
  • --be STRING β€” xNVMe backend, e.g. 'linux', 'spdk', 'fbsd', 'macos', 'posix', 'windows'
  • --dev-nsid 0xNUM β€” Namespace Identifier for Device Handle
  • --admin STRING β€” xNVMe admin. command-interface, e.g. 'nvme', 'block'
  • --mem STRING β€” xNVMe buffer/memory manager
  • --direct NUM β€” Bypass layers
  • --help β€” Show usage / help
🫠 real talk: --cdw4 0xNUM shows up twice in the option list up there, both times saying "Command Dword4". not me editing it, not me deleting it β€” i'm telling you exactly what the page says, and the page says it twice. periodt.

🌈 SEE ALSO 🌈

Full documentation at: <https://xnvme.io/> πŸ’–


🧚 AUTHOR 🧚

Written by Simon A. F. Lund <simon.lund@samsung.com> on behalf of Samsung


okay that's the whole page, you ate that, slay πŸ’…βœ¨

and a little sign-off for the fine print bestie: this is xNVMe, from 09 September 2024 β€” go build something iconic with it πŸŽ€πŸ¦‹πŸŒΈ

πŸ“¦ where this page comes from