Sponsor:

Your company here, and a link to your site. Click to find out more.

xnvme-pioc - Man Page

Pass a used-defined IO Command through

Synopsis

xnvme pioc <uri> [<args>]

Description

Pass a used-defined IO Command through

Required

<uri>

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

Optional

[ --cdw0 0xNUM ]

Command Dword0

[ --cdw1 0xNUM ]

Command Dword1

[ --cdw2 0xNUM ]

Command Dword2

[ --cdw3 0xNUM ]

Command Dword3

[ --cdw4 0xNUM ]

Command Dword4

[ --cdw4 0xNUM ]

Command Dword4

[ --cdw5 0xNUM ]

Command Dword5

[ --cdw6 0xNUM ]

Command Dword6

[ --cdw7 0xNUM ]

Command Dword7

[ --cdw8 0xNUM ]

Command Dword8

[ --cdw9 0xNUM ]

Command Dword9

[ --cdw10 0xNUM ]

Command Dword10

[ --cdw11 0xNUM ]

Command Dword11

[ --cdw12 0xNUM ]

Command Dword12

[ --cdw13 0xNUM ]

Command Dword13

[ --cdw14 0xNUM ]

Command Dword14

[ --cdw15 0xNUM ]

Command Dword15

[ --opcode 0xNUM ]

Command opcode

[ --nsid 0xNUM ]

Namespace Identifier for Command Construction

[ --data-input FILE ]

Path to data input-file

[ --data-output FILE ]

Path to data output-file

[ --data-nbytes NUM ]

Data size in bytes

[ --meta-input FILE ]

Path to meta input-file

[ --meta-output FILE ]

Path to meta output-file

[ --meta-nbytes NUM ]

Meta size in bytes

[ --verbose ]

Increase output info

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

[ --help ]

Show usage / help

See Also

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

Author

Written by Simon A. F. Lund <simon.lund@samsung.com> on behalf of Samsung

Referenced By

xnvme(1).

03 February 2024 xNVMe