test/nvme/xnvme: Add io_uring_cmdThis requires some extra dance since it seems it can work only on topof generic nvme char devices.Change-Id: I84a489b64bada9335a30f3db185edba3733b7902Signed-off
test/nvme/xnvme: Add io_uring_cmdThis requires some extra dance since it seems it can work only on topof generic nvme char devices.Change-Id: I84a489b64bada9335a30f3db185edba3733b7902Signed-off-by: Michal Berger <michal.berger@intel.com>Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/25308Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com>Community-CI: Community CI Samsung <spdk.community.ci.samsung@gmail.com>Reviewed-by: Jim Harris <jim.harris@nvidia.com>Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>Reviewed-by: Karl Bonde Torp <k.torp@samsung.com>Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com>
show more ...
test/common: Make sure get_nvmes_with_ns_management() doesn't report failureThis function is meant to simply list nvme devices which supportns management, it shouldn't trigger errexit (it's up to
test/common: Make sure get_nvmes_with_ns_management() doesn't report failureThis function is meant to simply list nvme devices which supportns management, it shouldn't trigger errexit (it's up to the caller toverify returned list of devices).Currently, this function may report failure in case last ctrl fromthe list doesn't have proper support enabled - this may be problematicin case there's a mix of different nvmes installed with differentcapabilities.Change-Id: I57d96a1404534003c8d1a46bf85eda6e316da529Signed-off-by: Michal Berger <michal.berger@intel.com>Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/24834Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com>Reviewed-by: Jim Harris <jim.harris@samsung.com>Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
tests: Move functions from cuse/common.sh to common/nvme/functions.shThese functions are not strictly related to CUSE, rather they aregeneric functions serving as wrappers around nvme-cli.Since
tests: Move functions from cuse/common.sh to common/nvme/functions.shThese functions are not strictly related to CUSE, rather they aregeneric functions serving as wrappers around nvme-cli.Since there's no obvious structure as to where similar functionsshould be placed start the trend of making them comfortable under:test/common/TOPIC/functions.sh.The autotest_common.sh and scripts/common.sh are already overloadedwith myriads of different functions so this should be considered asan entry to a bigger refactor dealing with shuffling these functionsinto proper location.Change-Id: I767aec2a8f49ddc95659e30fa1b04473d2689847Signed-off-by: Michal Berger <michal.berger@intel.com>Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/17851Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>Reviewed-by: Jim Harris <jim.harris@samsung.com>