Commit d0e6ba0a authored by Michal Berger's avatar Michal Berger Committed by Tomasz Zawadzki
Browse files

test/nvmf: Manually remove cpu lock files 



Signed-off-by: default avatarMichal Berger <michal.berger@intel.com>
Change-Id: Idcace2a8f7d47b9d508089b8171f1121fd819c82
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/15905


Reviewed-by: default avatarPawel Piatek <pawelx.piatek@intel.com>
Reviewed-by: default avatarKonrad Sztyber <konrad.sztyber@intel.com>
Reviewed-by: default avatarTomasz Zawadzki <tomasz.zawadzki@intel.com>
Tested-by: default avatarSPDK CI Jenkins <sys_sgci@intel.com>
parent 4f857ce5

test/nvmf/target/host_management.sh

+6 −0
Original line number Diff line number Diff line
@@ -90,6 +90,12 @@ function nvmf_host_management() { 
	# and so it will never shut down. Just kill it.

	kill -9 $perfpid || true



	# Since we abruptly terminate $perfpid above, we need to do some cleanup on our own.

	# In particular, we need to get rid of the cpu lock files that may potentially prevent

	# the next instance of bdevperf from running.

	# FIXME: Can't we just SIGTERM $perfpid above?

	rm -f /var/tmp/spdk_cpu_lock*



	# Run bdevperf

	$rootdir/build/examples/bdevperf -r /var/tmp/bdevperf.sock --json <(gen_nvmf_target_json "0") -q 64 -o 65536 -w verify -t 1