XNVME_TESTS_COMPARE-COMPARE(1)

📦 version 0.7.5, in alpine 3.24

💅 xnvme_tests_compare-compare 💅

okay so bestie, welcome to the xnvme_tests_compare-compare page — it's part of the xNVMe manual fam, and it's literally the whole vibe check for one lil tool. sit down, grab a strawberry 🍓, we're gonna get you fluent.

✨ NAME ✨

xnvme_tests_compare-compare — a basic test of compare functionality. that's it, that's the whole vibe 💖

🦋 SYNOPSIS 🦋

xnvme_tests_compare compare <uri> [<args>]

so you call the xnvme_tests_compare tool, hit it with the compare subcommand, hand it a <uri>, and then any <args> you want on top. slay. 🫶

🌸 DESCRIPTION 🌸

basic test of compare functionality. no cap, that's genuinely what it does — it exercises the compare thing and makes sure it's doing what it's supposed to. iconic behavior honestly. 👑

💜 REQUIRED 💜

  • <uri> — the device URI, aka where your device lives. examples of what this can look like: '/dev/nvme0n1', '0000:01:00.1', '10.9.8.1.8888', '\.PhysicalDrive1'. yes you need this. it's not optional, bestie. 🙈

🎀 OPTIONAL 🎀

these are the lil extras — you don't have to, but you can:

  • [ --slba 0xNUM ] — start Logical Block Address. where the party begins. starting point energy ✨
  • [ --nlb NUM ] — Number of LBAs. and pssst, careful: it's a zero-based value. do not come for me if you forget that. 😭
  • [ --subnqn STRING ] — the Subsystem NQN of the NVMe over Fabrics endpoint, e.g. 'nqn.2022-06.io.xnvme:ctrlnode1'. very long, very fancy, very NVMe-over-Fabrics. 💅
  • [ --hostnqn STRING ] — the host NQN you use when connecting to NVMe over Fabrics controllers. like your little name tag at the fabrics party 🎀
  • [ --be STRING ] — the xNVMe backend, e.g. 'linux', 'spdk', 'fbsd', 'macos', 'posix', 'windows'. pick your fighter 🔥
  • [ --dev-nsid 0xNUM ] — Namespace Identifier for the Device Handle. which namespace are we talking to, bestie? 🌈
  • [ --admin STRING ] — the xNVMe admin. command-interface, e.g. 'nvme', 'block'. choose your admin lane ⭐
  • [ --mem STRING ] — the xNVMe buffer/memory manager. gotta manage that memory somehow, we love a responsible icon 💖
  • [ --direct NUM ] — Bypass layers. yes, literally, it bypasses layers. dramatic but valid. 💀
  • [ --sync STRING ] — the xNVMe sync. command-interface, e.g. 'nvme', 'block'. keeping it in sync, as one does 🧚
  • [ --help ] — Show usage / help. the classic. when in doubt, --help it out 🫶

🌟 SEE ALSO 🌟

full documentation is right here at <https://xnvme.io/> — go drink from the firehose, bestie. iykyk. 🦋

👑 AUTHOR 👑

Written by Simon A. F. Lund <simon.lund@samsung.com> on behalf of Samsung. absolute main character energy, we stan. 🌈

ngl, that's the whole page. no notes. go forth and compare. ✨

mwah 💋 — this was xNVMe, dated 09 September 2024, and you just read the whole xnvme_tests_compare-compare moment. periodt. 💅🎀🦋

📦 where this page comes from