test/vfio_user: use 2048MiB static memory size for bdevperf

Previously we use 1024MiB static memory for bdevperf, but it may invoke
DPDK dynamic memory allocation when calling `spdk_zmalloc`, and this
part of new memory region isn't registered to remote target process,
vfio-user like solution is designed for pre-allocated memory, so here
we can increase the static memory size as a workaround.

Also add debug log when testing.

Fix issue #2846.

Change-Id: I509093a12a63db2c9e9797da10eab9b5ee0b3aac
Signed-off-by: Changpeng Liu <changpeng.liu@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/16141
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Reviewed-by: Shuhei Matsumoto <smatsumoto@nvidia.com>
This commit is contained in:
Changpeng Liu 2023-01-04 15:59:03 +08:00 committed by Tomasz Zawadzki
parent 312a6511db
commit eb5789ceae

View File

@ -13,7 +13,7 @@ rm -rf $vfu_dir
mkdir -p $vfu_dir
# Start `spdk_tgt` and configure it
$SPDK_BIN_DIR/spdk_tgt -m 0xf &
$SPDK_BIN_DIR/spdk_tgt -m 0xf -L vfu_virtio &
spdk_tgt_pid=$!
waitforlisten $spdk_tgt_pid
@ -37,7 +37,7 @@ $rpc_py vfu_virtio_scsi_add_target vfu.scsi --scsi-target-num=1 --bdev-name mall
bdevperf=$rootdir/build/examples/bdevperf
bdevperf_rpc_sock=/tmp/bdevperf.sock
$bdevperf -r $bdevperf_rpc_sock -g -s 1024 -q 256 -o 4096 -w randrw -M 50 -t 30 -m 0xf0 &
$bdevperf -r $bdevperf_rpc_sock -g -s 2048 -q 256 -o 4096 -w randrw -M 50 -t 30 -m 0xf0 -L vfio_pci -L virtio_vfio_user &
bdevperf_pid=$!
trap 'killprocess $bdevperf_pid; exit 1' SIGINT SIGTERM EXIT
waitforlisten $bdevperf_pid $bdevperf_rpc_sock