It's not providing a lot of value, while being pretty problematic, as the read is blocking and cannot be easily changed to be non-blocking, as dump_info_json is a synchronous interface. Now that dump_info_json isn't using any synchronous interfaces from the NVMe driver, we can send a bdev_get_bdevs call in the async_init.sh test to verify that. Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Change-Id: Ida31c8d1000a52b0782f698afe46b071ed4e41df Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9488 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> |
||
---|---|---|
.. | ||
aer.sh | ||
async_init.sh | ||
bdevperf.sh | ||
dma.sh | ||
fio.sh | ||
identify_kernel_nvmf.sh | ||
identify.sh | ||
multicontroller.sh | ||
multipath.sh | ||
perf.sh | ||
target_disconnect.sh |