XNVME_TESTS_MAP-MEM_MAP_UNMAP(1)
π xnvme_tests_map-mem_map_unmap(1) β aka the xNVMe manual, bestie edition π
okay so you found the xnvme_tests_map-mem_map_unmap page in the xNVMe manual and you're like "what is this" β don't worry, I got you. sit down, hydrate, let's go β¨
πΈ NAME πΈ
xnvme_tests_map-mem_map_unmap β it maps and unmaps a buffer 'count' times, of size [1, 2^count]. literally that's the whole personality π
π¦ SYNOPSIS π¦
xnvme_tests_map mem_map_unmap <uri> [<args>]
that's it, that's the shape of it. xnvme_tests_map is the command, mem_map_unmap is the sub-command, then your <uri> and then whatever optional <args> you feel like sprinkling in π«Ά
π DESCRIPTION π
Map and unmap a buffer 'count' times of size [1, 2^count]. no cap, that is genuinely what it does β it's a stress-y little map/unmap loop and it's kind of iconic for it π₯
π REQUIRED π
these ones are not optional, bestie. you need them. no skipping π
<uri>β the Device URI, like'/dev/nvme0n1','0000:01:00.1','10.9.8.1.8888', or'\.PhysicalDrive1'. yes, all of those, character for character, I don't make the rules β¨--count NUMβ use the given'NUM'as the count. that's the number of times it does the map/unmap thing π«
π OPTIONAL π
the little extras, the accessories to the outfit. all optional, all cute π
[ --subnqn STRING ]β the Subsystem NQN of the NVMe over Fabrics endpoint, e.g.'nqn.2022-06.io.xnvme:ctrlnode1'. for the fabrics girlies π§[ --hostnqn STRING ]β the host NQN to use when connecting to NVMe over Fabrics controllers π¦[ --be STRING ]β the xNVMe backend, e.g.'linux','spdk','fbsd','macos','posix','windows'. pick your fighter π[ --dev-nsid 0xNUM ]β Namespace Identifier for Device Handle. note the0x, it's giving hex and we respect it β[ --admin STRING ]β the xNVMe admin. command-interface, e.g.'nvme','block'π[ --mem STRING ]β the xNVMe buffer/memory manager πΈ[ --direct NUM ]β Bypass layers. yes, all of them, go off π[ --help ]β Show usage / help. your bestie when you're lost π«Ά
π SEE ALSO π
Full documentation at: <https://xnvme.io/> β go read it, it's the main character of the docs, iykyk π
β AUTHOR β
Written by Simon A. F. Lund <simon.lund@samsung.com> on behalf of Samsung. shoutout, legend behaviour fr fr π
lowkey reminder: every flag and value up there is exactly as written β don't go freestyling on the option names, bestie π
and that's the page!! π source/version is xNVMe, dated 09 September 202X β mwah, go map some buffers, slay, periodt π β¨
π¦ where this page comes from
- alpine 3.24: xnvme-doc 0.7.5-r1 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms