ivampiresp/Spdk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

test/nvmf: Perf test uses preallocated memory

Browse Source 
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 <seth.howell@intel.com>
Reviewed-on: https://review.gerrithub.io/435942
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Reviewed-by: Changpeng Liu <changpeng.liu@intel.com>
Reviewed-by: Ben Walker <benjamin.walker@intel.com>
This commit is contained in:
Seth Howell 2018-12-03 14:16:49 -07:00 committed by Ben Walker
parent fd985a47dd
commit 8431fb1196
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
test/nvmf/host/perf.sh
View File

@ -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