The target is allowed to change the number of i/o queues. test if the host is able to reconnect in this scenario. I was able to test this successfully with tcp and rdma. fc still fails due to the race condition in the target code. Next attempt to get this series upstream :) This version is based on my previous posted nvme/047 patches [1] [1] https://lore.kernel.org/linux-nvme/20230329090202.8351-1-dwagner@xxxxxxx/ v5: - moved generic parts to nvme/rc - renamed test to 048 - rebased ontop of nvme/047 v4: - do not remove ports instead depend on host removing controllers, see https://lore.kernel.org/linux-nvme/20220927143157.3659-1-dwagner@xxxxxxx/ - https://lore.kernel.org/linux-nvme/20220927143719.4214-1-dwagner@xxxxxxx/ v3: - Added comment why at least 2 CPUs are needed for the test - Fixed shell quoting in _set_nvmet_attr_qid_max - https://lore.kernel.org/linux-nvme/20220913065758.134668-1-dwagner@xxxxxxx/ v2: - detect if attr_qid_max is available - https://lore.kernel.org/linux-block/20220831153506.28234-1-dwagner@xxxxxxx/ v1: - https://lore.kernel.org/linux-block/20220831120900.13129-1-dwagner@xxxxxxx/ Daniel Wagner (4): nvme/rc: Add setter for attr_qid_max nvme/rc: Add nvmet attribute feature detection function nvme/rc: Add helper to wait for nvme ctrl state nvme/048: test queue count changes on reconnect tests/nvme/048 | 81 ++++++++++++++++++++++++++++++++++++++++++++++ tests/nvme/048.out | 3 ++ tests/nvme/rc | 58 +++++++++++++++++++++++++++++++++ 3 files changed, 142 insertions(+) create mode 100755 tests/nvme/048 create mode 100644 tests/nvme/048.out -- 2.40.0
