Spdk/test/nvmf
Krzysztof Karas 0af934b38c event: add CPU lock files
When running SPDK application on a given set of
CPU cores, create lock files for each of them.
This wil prevent user misconfiguration and
assigning a core to more than one SPDK instance.

The introduced mechanism is based on device locks
implemented in spdk_pci_device_claim() function.

Add a command line option to disable lock files.
This feature will be useful in cases where differing
CPU cores is impossible (eg. setup with only one core
available).

The patch also fixes all existing cases of overlapping
core masks.

Change-Id: Ie9aacb7523a3597b9aa20f2c3fa9efe4db92c44c
Signed-off-by: Krzysztof Karas <krzysztof.karas@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/14919
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Community-CI: Mellanox Build Bot
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Reviewed-by: Shuhei Matsumoto <smatsumoto@nvidia.com>
2022-11-09 08:18:32 +00:00
..
host event: add CPU lock files 2022-11-09 08:18:32 +00:00
target event: add CPU lock files 2022-11-09 08:18:32 +00:00
common.sh test/nvmf: Test different abort qd sizes under SPDK and kernel targets 2022-09-19 13:13:42 +00:00
nvmf.sh autotest: Move nvmf's fuzzing outside the main suite 2022-09-20 00:46:11 +00:00
README.md test: add parse_common_script_args function 2019-05-22 23:43:51 +00:00

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.