XNVME_TESTS_ASYNC_INTF-INIT_TERM(1)

📦 version 0.7.5, in alpine 3.24

💅 xnvme_tests_async_intf init_term 💅

okay bestie, so this is the xnvme_tests_async_intf-init_term manual page — section 1 of the xNVMe manual, aka the sparkly little corner of the docs where you go to spin up a whole bunch of async contexts at a given queue depth. pull up a chair, we're doing this 🫶

✨ NAME ✨

xnvme_tests_async_intf-init_term — create count contexts with the given qdepth, periodt. that's the whole vibe 💖

🌸 SYNOPSIS 🌸

xnvme_tests_async_intf init_term <uri> [<args>]

🦋 DESCRIPTION 🦋

the way this one is literally just: create count contexts with the given qdepth. iconic, minimal, no notes. you hand it a uri, you tell it how many contexts you want and how deep the queue goes, and it does the thing ✨

💖 REQUIRED 💖

these are not optional, bestie. you need them. no cap.

  • <uri> — the Device URI, i.e. the address of the thing you're talking to. examples of what that looks like: '/dev/nvme0n1', '0000:01:00.1', '10.9.8.1.8888', '\.PhysicalDrive1' 👑
  • --count NUM — use the given NUM as the count. yes, the count. that's the assignment and it ate 💅
  • --qdepth NUM — use the given NUM as the queue max capacity. deceptively simple, lowkey powerful 🌈

🎀 OPTIONAL 🎀

the little extras. the sprinkles on the async cupcake 🧚

  • [ --clear ] — clear something… and yes, that is genuinely all the original says about it. mysterious main character energy 🙈
  • [ --subnqn STRING ] — the 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. you know, the whole NQN situation 🎀
  • [ --be STRING ] — the xNVMe backend, e.g. 'linux', 'spdk', 'fbsd', 'macos', 'posix', 'windows'. pick your fighter 💀
  • [ --dev-nsid 0xNUM ] — the Namespace Identifier for the Device Handle. hex-coded, naturally 0xNUM ⭐
  • [ --admin STRING ] — the xNVMe admin. command-interface, e.g. 'nvme', 'block' 👑
  • [ --mem STRING ] — the xNVMe buffer/memory manager. memory management but make it cute 🌸
  • [ --direct NUM ] — bypass layers. straight through, no detours, main character route 🔥
  • [ --sync STRING ] — the xNVMe sync. command-interface, e.g. 'nvme', 'block' 💜
  • [ --async STRING ] — the xNVMe async. command-interface, e.g. 'io_uring', 'emu'. the whole point of this test, fr fr 🦋
  • [ --help ] — show usage / help. when in doubt, ask for help, that's growth 🫶
✨ friendly reminder: the REQUIRED ones are required. if you skip --count or --qdepth the vibe check will not pass and nothing is going to slay.

👀 SEE ALSO 👀

full documentation at: <https://xnvme.io/> — go read it, iykyk 💖

🌈 AUTHOR 🌈

written by Simon A. F. Lund <simon.lund@samsung.com> on behalf of Samsung. thank you for your service, king 👑✨

and that's the page, bestie!! this was xNVMe (09 September) dropping the XNVME_TESTS_ASYNC_INTF-INIT_TERM(1) page — go forth and init_term responsibly 💅🎀💖

📦 where this page comes from