From 8431fb119618a356cf8d1bc567f1d1059ee87baf Mon Sep 17 00:00:00 2001 From: Seth Howell Date: Mon, 3 Dec 2018 14:16:49 -0700 Subject: [PATCH] test/nvmf: Perf test uses preallocated memory There appear to be issues around using dynamic memory allocation with secondary processes and local NVMe drives. This change allows us to keep running the NVMe-oF physical tests while we debug the root cause of the issue. Change-Id: I2fdbac9878c3e19e6ef0bcef1aa301b7062dc0bf Signed-off-by: Seth Howell Reviewed-on: https://review.gerrithub.io/435942 Tested-by: SPDK CI Jenkins Chandler-Test-Pool: SPDK Automated Test System Reviewed-by: Jim Harris Reviewed-by: Changpeng Liu Reviewed-by: Ben Walker --- test/nvmf/host/perf.sh | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/test/nvmf/host/perf.sh b/test/nvmf/host/perf.sh index 32202f0ab..46f0bcb61 100755 --- a/test/nvmf/host/perf.sh +++ b/test/nvmf/host/perf.sh @@ -24,7 +24,11 @@ fi timing_enter perf timing_enter start_nvmf_tgt -$NVMF_APP -m 0xF & +# Start the NVMe-oF target with preallocated memory because we will need to run perf.c +# as a secondary process later, and secondary process memory allocation is broken with +# the IOMMU. +# todo: remove this when the proper fixes are merged into DPDK. +$NVMF_APP -m 0xF -s 4096 & nvmfpid=$! trap "process_shm --id $NVMF_APP_SHM_ID; killprocess $nvmfpid; exit 1" SIGINT SIGTERM EXIT