ivampiresp/Spdk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
5d5d45c8c3
Spdk/test/nvmf
History
Jim Harris d8e11195cc test: use single core when testing nvme fuzz with nvmf target 
There's really no need to specify 4 cores for both the fuzz app
and the nvmf target, since only one is ever used.  Reducing the
mask to a single core each makes the fuzz.sh tests easier to run
in VMs with a limited number of cores.

Signed-off-by: Jim Harris <james.r.harris@intel.com>
Change-Id: Id956ac8d0d7f75cb0e76b78c9175b4aa520218bf
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9725
Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2022-06-30 13:32:25 -04:00
..
host bdev/nvme: remove CSTS from driver-specific JSON info 2022-06-30 13:32:25 -04:00
target test: use single core when testing nvme fuzz with nvmf target 2022-06-30 13:32:25 -04:00
common.sh test/nvmf: always use loopback when running tests in --iso mode 2022-06-30 13:32:25 -04:00
nvmf.sh test/nvmf: add asynchronous NVMe initialization test 2022-06-30 13:32:25 -04:00
README.md test: add parse_common_script_args function 2019-05-22 23:43:51 +00:00

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.