examples: rename ioat perf tool to ioat_perf

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>
This commit is contained in:
Jim Harris 2019-05-21 04:46:47 -07:00
parent bf647c168a
commit 9018dd60c6
4 changed files with 4 additions and 4 deletions

View File

@ -1 +1 @@
perf
ioat_perf

View File

@ -34,7 +34,7 @@
SPDK_ROOT_DIR := $(abspath $(CURDIR)/../../..)
include $(SPDK_ROOT_DIR)/mk/spdk.common.mk
APP = perf
APP = ioat_perf
C_SRCS := perf.c

View File

@ -400,7 +400,7 @@ init(void)
struct spdk_env_opts opts;
spdk_env_opts_init(&opts);
opts.name = "perf";
opts.name = "ioat_perf";
opts.core_mask = g_user_config.core_mask;
if (spdk_env_init(&opts) < 0) {
return -1;

View File

@ -9,7 +9,7 @@ source $rootdir/test/common/autotest_common.sh
timing_enter ioat
timing_enter perf
$rootdir/examples/ioat/perf/perf -t 1
$rootdir/examples/ioat/perf/ioat_perf -t 1
timing_exit perf
timing_enter verify