XNVME_FILE-DUMP-ASYNC-IOVEC(1)

📦 version 0.7.5, in alpine 3.24, epel 9, fedora 43, fedora 44

💖 XNVME_FILE-DUMP-ASYNC-IOVEC 💖

okay bestie, welcome to the xNVMe manual page for xnvme_file-dump-async-iovec, living in section 1 of the xNVMe manual. sit down, grab a strawberry 🍓, and let's get into it.

✨ NAME ✨

xnvme_file-dump-async-iovec — write a buffer of 'data-nbytes' to file --data-output

like. that's the whole job. it writes a buffer. a chunk of bytes. into a file. and it does it async. slay 💅

🌸 SYNOPSIS 🌸

xnvme_file dump-async-iovec <data-output> [<args>]

so you call xnvme_file, you tell it dump-async-iovec, you hand it your <data-output>, and then whatever <args> you want on top. simple as. ✨

🦋 DESCRIPTION 🦋

Write a buffer of 'data-nbytes' to file --data-output.

no cap, that's it. that's the vibe. it's an async, iovec-flavoured dump of data straight into a file of your choosing. it's giving "I have bytes and I know where they're going" energy 👑

👑 REQUIRED 👑

these are non-negotiable bestie, you literally cannot run this without them 😭

  • <data-output> — the path to your data output-file. where the bytes go. that's the whole point.
  • --data-nbytes NUM — the data size, in bytes. how much data are we talking? NUM. that much.

🎀 OPTIONAL 🎀

these are the little extras, the accessories to the outfit, the butterfly clips in the hair 🦋

  • [ --iosize NUM ] — use the given NUM as the bs/iosize.
  • [ --qdepth NUM ] — use the given NUM as the queue max capacity.
  • [ --direct ] — bypass layers. just straight through. no detours. 🚀
  • [ --async STRING ] — the xNVMe async. command-interface, like 'io_uring' or 'emu'.
  • [ --be STRING ] — the xNVMe backend, like 'linux', 'spdk', 'fbsd', 'macos', 'posix', or 'windows'. pick your fighter 💀
  • [ --vec-cnt NUM ] — the number of elements in vectors when doing vectored IOs. it's giving scatter-gather, it's giving iovec realness.
  • [ --help ] — show usage / help. when in doubt, ask for help. no shame, bestie 🫶

🌈 SEE ALSO 🌈

full documentation at: <https://xnvme.io/>

go read it. it's iconic. iykyk ✨

💜 AUTHOR 💜

written by Simon A. F. Lund <simon.lund@samsung.com> on behalf of Samsung. we love a credited author, periodt 💅

xNVMe · 09 September 2024 · and that's the whole page bestie, go write some bytes, you ate 💖🌈⭐

📦 where this page comes from