xnvme_tests_async_intf-init_term - Create 'count' contexts with given 'qdepth'

NAME  SYNOPSIS  DESCRIPTION  REQUIRED  OPTIONAL  SEE ALSO  AUTHOR 

---

NAME

xnvme_tests_async_intf-init_term - Create ’count’ contexts with given ’qdepth’

SYNOPSIS

xnvme_tests_async_intf init_term <uri> [<args>]

DESCRIPTION

Create ’count’ contexts with given ’qdepth’

REQUIRED

<uri>

Device URI e.g. ’/dev/nvme0n1’, ’0000:01:00.1’, ’10.9.8.1.8888’, ’\.PhysicalDrive1’

--count NUM

Use given ’NUM’ as count

--qdepth NUM

Use given ’NUM’ as queue max capacity

OPTIONAL

[ --clear ]

Clear something...

[ --subnqn STRING ]

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

[ --be STRING ]

xNVMe backend, e.g. ’linux’, ’spdk’, ’fbsd’, ’macos’, ’posix’, ’windows’

[ --dev-nsid 0xNUM ]

Namespace Identifier for Device Handle

[ --admin STRING ]

xNVMe admin. command-interface, e.g. ’nvme’, ’block’

[ --mem STRING ]

xNVMe buffer/memory manager

[ --direct NUM ]

Bypass layers

[ --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

SEE ALSO

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

AUTHOR

Written by Simon A. F. Lund <[email protected]> on behalf of Samsung

---