Spdk/test/dpdk_memory_utility/test_dpdk_mem_info.sh

#!/usr/bin/env bash

testdir=$(readlink -f $(dirname $0))
rootdir=$(readlink -f $testdir/../..)
source $rootdir/test/common/autotest_common.sh

MEM_SCRIPT="$rootdir/scripts/dpdk_mem_info.py"

"${SPDK_APP[@]}" &
spdkpid=$!

waitforlisten $spdkpid

trap 'killprocess $spdkpid' SIGINT SIGTERM EXIT

$rpc_py env_dpdk_get_mem_stats

$MEM_SCRIPT

$MEM_SCRIPT -m 0

trap - SIGINT SIGTERM EXIT
killprocess $spdkpid
test: add test to validate dpdk mem utility This test essentially confirms that the new RPC properly creates a test file and that the script can parse that file and run through a basic set of operations and exit without an error. Change-Id: Idf0c831020696a3a62fcef13171eedf3fcf63f5b Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/477867 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> 2019-12-12 21:41:38 +00:00			`#!/usr/bin/env bash`

			`testdir=$(readlink -f $(dirname $0))`
			`rootdir=$(readlink -f $testdir/../..)`
			`source $rootdir/test/common/autotest_common.sh`

			`MEM_SCRIPT="$rootdir/scripts/dpdk_mem_info.py"`

check_format: Ignore shellcheck's SC2128 and SC2178 directives These are currently prone to false-positives especially in terms of scoping. Consider the following: foo() { local bar=(42) echo "${bar[*]}" } bar=43 foo echo "$bar" Some versions of shellcheck, including the latest, 0.7.2, complain about $bar being reused as a plain string here. This is incorrect since foo() holds its own copy of bar[@] hence the assignment which takes place outside of it doesn't affect its content. SC2178 can be mitigated be reversing the order of declaration: bar=43 foo() { ... } ... but the SC2128 still remains. Currently, in our code majority of these warnings are coming from false-positives due to initial source'ing which most of our test scripts do (e.g. they fetch a function where local bar=() is used and in the test itself $bar happens to be assigned a plain string. This is still valid code). To mitigate, disable these directives untill shellcheck is capable of properly interpreting scoping when checking them. Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: Ifbde973eae6e261d79e1c340eb28644bce5f4e45 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/8503 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> 2021-06-24 14:44:45 +00:00			`"${SPDK_APP[@]}" &`
test: add test to validate dpdk mem utility This test essentially confirms that the new RPC properly creates a test file and that the script can parse that file and run through a basic set of operations and exit without an error. Change-Id: Idf0c831020696a3a62fcef13171eedf3fcf63f5b Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/477867 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> 2019-12-12 21:41:38 +00:00			`spdkpid=$!`

			`waitforlisten $spdkpid`

			`trap 'killprocess $spdkpid' SIGINT SIGTERM EXIT`

			`$rpc_py env_dpdk_get_mem_stats`

			`$MEM_SCRIPT`

			`$MEM_SCRIPT -m 0`

			`trap - SIGINT SIGTERM EXIT`
			`killprocess $spdkpid`