Spdk/test/env/env.sh
Darek Stojaczyk 0f068a6b65 test/env_dpdk_post_init: use only a single core
Starting DPDK on all cores causes fairly frequent hangs
on one of our CI BSD systems, so we limit DPDK to just
the first CPU core. This will let our CI pass while we
investigate the real issue.

Change-Id: Iaa5b665b1364acd04555063677adbd12230ed992
Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
Reviewed-on: https://review.gerrithub.io/c/441567
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-22 14:01:57 +00:00

39 lines
953 B
Bash
Executable File

#!/usr/bin/env bash
set -e
testdir=$(readlink -f $(dirname $0))
rootdir=$(readlink -f $testdir/../..)
source $rootdir/test/common/autotest_common.sh
timing_enter env
timing_enter memory
$testdir/memory/memory_ut
timing_exit memory
timing_enter vtophys
$testdir/vtophys/vtophys
timing_exit vtophys
timing_enter pci
$testdir/pci/pci_ut
timing_exit pci
timing_enter env_dpdk_post_init
argv="-c 0x1 "
if [ `uname` = Linux ]; then
# The default base virtaddr falls into a region reserved by ASAN.
# DPDK will try to find the nearest available address space by
# trying to do mmap over and over, which will take ages to finish.
# We speed up the process by specifying an address that's not
# supposed to be reserved by ASAN. Regular SPDK applications do
# this implicitly.
argv+="--base-virtaddr=0x200000000000"
fi
$testdir/env_dpdk_post_init/env_dpdk_post_init $argv
timing_exit env_dpdk_post_init
report_test_completion "env"
timing_exit env