Previously the Transport IDs would need to be an ini-style config file that the nvme_fuzz app would then parse. Instead just add a -F option that tells the nvme_fuzz app which subsystem(s) to fuzz. This simplifies the fuzz_app code a bit and makes it a bit easier to use. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I622f5173ff36e15d653155c4eb7eaaecb5564818 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9603 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> |
||
---|---|---|
.. | ||
host | ||
target | ||
common.sh | ||
nvmf.sh | ||
README.md |
NVMe-oF test scripts
The test scripts in this directory hierarchy can be run in isolation by passing the --iso flag when running the test script. This will set up the RDMA NIC for testing and then tear it back down again when the test is completed.