XNVME_TESTS_ZN...-FLUSH-EXPLICIT(1)

πŸ“¦ version 0.7.5, in alpine 3.24

✨ NAME ✨

xnvme_tests_znd_zrwa-flush-explicit β€” okay bestie, this is the one that verifies operation of explicit-flush πŸ’… and yes it lives in the xNVMe manual, so you already know it's about to be a whole thing πŸ¦‹


🌸 SYNOPSIS 🌸

xnvme_tests_znd_zrwa flush-explicit <uri> [<args>]

like literally that's it, that's the whole vibe check πŸ‘‘


πŸ’– DESCRIPTION πŸ’–

Verify operation of explicit-flush ✨

ngl it's doing exactly what it says on the tin β€” the whole main character energy here is verifying that explicit-flush behaves. no cap πŸ’€


πŸŽ€ REQUIRED πŸŽ€

  • <uri> β€” the device URI, periodt. like for real, examples include '/dev/nvme0n1', '0000:01:00.1', '10.9.8.1.8888', and '\.PhysicalDrive1' 🫢 (yes that last one has a backslash in front of the dot, copy it exactly, iykyk)

⭐ OPTIONAL ⭐

  • [ --slba 0xNUM ] β€” Start Logical Block Address 🌸 (it's a hex 0xNUM situation, don't @ me)
  • [ --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 πŸ‘‘
  • [ --sync STRING ] β€” xNVMe sync. command-interface, e.g. 'nvme', 'block' ⭐
  • [ --async STRING ] β€” xNVMe async. command-interface, e.g. 'io_uring', 'emu' πŸ’€
  • [ --help ] β€” Show usage / help πŸ™ˆ (the eternal savior, honestly)

🧚 SEE ALSO 🧚

Full documentation at: <https://xnvme.io/> β€” go drink from the firehose bestie πŸ’–


🌺 AUTHOR 🌺

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


lowkey reminder: everything above is literal, so keep those flags character-for-character β€” 0xNUM, STRING, NUM, and every example path stay exactly as written πŸ’…

xNVMe πŸ¦‹ 09 September πŸŽ€ β€” that's the source/version and date bestie, mwah, go slay your explicit-flush testing πŸ’–βœ¨πŸŒΈ

πŸ“¦ where this page comes from