+0
−7
+96
−113
Loading
Script was written in such a way that tests would be performed starting with all found NVMe disks in configuration. Then the number of disks for the workload would be reduced in loop until reaching 1. This is the scenario used in test case 1, described in SPDK NVMe Performance Benchmark document. --disk-no allowed to avoid running test in loop, and specify just a single value for the number of disks to be tested. Both loop logic and --disk-no are no longer required as tests are scheduled and run via CI system which picks the parameters for each test run. Change-Id: Iad0f4d0d259ac64680fd5bb69d7cbb7e0afff79c Signed-off-by:Karol Latecki <karol.latecki@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/3295 Community-CI: Mellanox Build Bot Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by:
Paul Luse <paul.e.luse@intel.com> Reviewed-by:
Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by:
Jim Harris <james.r.harris@intel.com>