XNVME_TESTS_ZN...-FLUSH-IMPLICIT(1)

📦 version 0.7.5, in alpine 3.24

💅 NAME 💅

xnvme_tests_znd_zrwa-flush-implicit — bestie, this one's here to verify operation of implicit-flush. That's it, that's the whole gig ✨

🎀 SYNOPSIS 🎀

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

So you run the flush-implicit subcommand, you hand it a <uri>, and then any <args> you feel like sprinkling on top 🫶

🌸 DESCRIPTION 🌸

Okay so real talk: this test literally verifies the operation of implicit-flush. No cap. That's the assignment and it ate 💅

⭐ REQUIRED ⭐

  • <uri> — the device URI, like the address of the thing you're talking to. Examples, verbatim, no editing: '/dev/nvme0n1', '0000:01:00.1', '10.9.8.1.8888', '\.PhysicalDrive1'. Pick the one that matches your setup, queen 👑

🦋 OPTIONAL 🦋

  • [ --slba 0xNUM ] — Start Logical Block Address. Give it a 0xNUM and that's where the party starts 🔥
  • [ --subnqn STRING ] — Subsystem NQN of the NVMe over Fabrics endpoint, e.g. 'nqn.2022-06.io.xnvme:ctrlnode1'. That string is the exact one from the docs, copy it as-is bestie 🧚
  • [ --hostnqn STRING ] — the host NQN you use when connecting to NVMe over Fabrics controllers. Yes, the controller needs to know who you are 🫶
  • [ --be STRING ] — xNVMe backend. Your choices, literally listed: 'linux', 'spdk', 'fbsd', 'macos', 'posix', 'windows' 👑
  • [ --dev-nsid 0xNUM ] — Namespace Identifier for Device Handle. A 0xNUM, very demure, very namespace ✨
  • [ --admin STRING ] — xNVMe admin. command-interface, e.g. 'nvme', 'block'. Admin stuff, iykyk 💅
  • [ --mem STRING ] — xNVMe buffer/memory manager. Where your buffers live their best life 🎀
  • [ --direct NUM ] — Bypass layers. Just a NUM, straight through, main character energy 🌈
  • [ --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. When in doubt, ask for help, that's growth 💖
Fr fr, those brackets mean optional. <uri> doesn't have brackets, so yeah, that one's mandatory 🙈

🔍 SEE ALSO 🔍

Full documentation at: <https://xnvme.io/> — go click it, it's giving resources 🌈

💜 AUTHOR 💜

Written by Simon A. F. Lund <simon.lund@samsung.com> on behalf of Samsung. Respect the author, the author ate 👑

Love you bestie, go flush some implicit stuff responsibly 🍓

Signed off with love — that's xNVMe, dated 09 September, from the XNVME_TESTS_ZN...-FLUSH-IMPLICIT(1) manual page. Slay 💅✨

📦 where this page comes from