9018dd60c6
This avoids conflict with the nvme perf tool. PGO gets confused during building - we may have data for nvme/perf which it then tries to use when building ioat/perf. Renaming the ioat perf tool fixes that problem. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Ib1084d56d671e44027ea05f453075a723f067580 Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/455320 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
21 lines
380 B
Bash
Executable File
21 lines
380 B
Bash
Executable File
#!/usr/bin/env bash
|
|
|
|
set -xe
|
|
|
|
testdir=$(readlink -f $(dirname $0))
|
|
rootdir=$(readlink -f $testdir/../..)
|
|
source $rootdir/test/common/autotest_common.sh
|
|
|
|
timing_enter ioat
|
|
|
|
timing_enter perf
|
|
$rootdir/examples/ioat/perf/ioat_perf -t 1
|
|
timing_exit perf
|
|
|
|
timing_enter verify
|
|
$rootdir/examples/ioat/verify/verify -t 1
|
|
timing_exit verify
|
|
|
|
report_test_completion "ioat"
|
|
timing_exit ioat
|