c930efda28
We apply ADQ on target, then run perf, so that we can verify SPDK implementation interacting with ADQ. Although the functional test cases here are relatively simplified, and in the CI, we have to add -debug compilation option, so the perf performance with ADQ may not be ideal. We will give another performance test reference cases of ADQ later. Change-Id: I5341a7fcd61334ef78084302a4ae70f8ec9b9e46 Signed-off-by: wanghailiangx <hailiangx.e.wang@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/7476 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Kamil Godzwon <kamilx.godzwon@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Xiaodong Liu <xiaodong.liu@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.