We have a collection of nvme tests, but all run with nvme-loop. This is the easiest to run on a standalone machine. However its very much possible to run nvme-tcp and nvme-rdma using a loopback network. Add capability to run tests with a new environment variable to set the transport type $nvme_trtype. $ nvme_trtype=[loop|tcp|rdma] ./check test/nvme This buys us some nice coverage on some more transport types. We also add some transport type specific helpers to mark tests that are relevant only for a single transport. Sagi Grimberg (6): nvme: consolidate nvme requirements based on transport type nvme: consolidate some nvme-cli utility functions nvme: make tests transport type agnostic tests/nvme: restrict tests to specific transports nvme: support nvme-tcp when runinng tests nvme: support rdma transport type tests/nvme/002 | 8 ++-- tests/nvme/003 | 10 ++-- tests/nvme/004 | 12 +++-- tests/nvme/005 | 15 +++--- tests/nvme/006 | 7 +-- tests/nvme/007 | 5 +- tests/nvme/008 | 13 +++--- tests/nvme/009 | 11 +++-- tests/nvme/010 | 13 +++--- tests/nvme/011 | 13 +++--- tests/nvme/012 | 14 +++--- tests/nvme/013 | 13 +++--- tests/nvme/014 | 13 +++--- tests/nvme/015 | 12 +++-- tests/nvme/016 | 7 +-- tests/nvme/017 | 7 +-- tests/nvme/018 | 13 +++--- tests/nvme/019 | 13 +++--- tests/nvme/020 | 11 +++-- tests/nvme/021 | 13 +++--- tests/nvme/022 | 13 +++--- tests/nvme/023 | 13 +++--- tests/nvme/024 | 13 +++--- tests/nvme/025 | 13 +++--- tests/nvme/026 | 13 +++--- tests/nvme/027 | 13 +++--- tests/nvme/028 | 15 +++--- tests/nvme/029 | 13 +++--- tests/nvme/030 | 8 ++-- tests/nvme/031 | 12 ++--- tests/nvme/032 | 4 ++ tests/nvme/rc | 122 +++++++++++++++++++++++++++++++++++++++++++++---- 32 files changed, 309 insertions(+), 166 deletions(-) -- 2.25.1
