Loading
test/nvmf_perf_adq: use proper sock implementation
In ADQ tests, the sock_impl_set_options RPC call is used to configure placement for given sock implementation to test Application Device Queues (ADQ) functionality. However, the test script configured placement always for posix sockets, while by default uring sockets are enabled. This caused the tests were failing. Before the sock_impl_set_options is used to configure options, we must retrieve current default socket implementation by a call to sock_get_default_impl() RPC function. Then use it in sock_set_default_impl RPC call. nvmf statistics reading is now done in a separate line, so they are now visible in the build log. Can speed up debugging in the future. Fixes #3090 Change-Id: I5e50ee79a9ab6bfa41d4c87c6b746e4985ac3f22 Signed-off-by:Marcin Spiewak <marcin.spiewak@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/22881 Reviewed-by:
Jim Harris <jim.harris@samsung.com> Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by:
Konrad Sztyber <konrad.sztyber@intel.com>