On 17/09/2025 12:49, Shin'ichiro Kawasaki wrote:
As of today, each of blktests test cases implement test() or
test_device(). When test() is implemented, the test case prepares test
target device by itself. When test_device() is implemented, the test
case is run for one of the device in TEST_DEVS that users prepare and
define in the config file. In other words, blktests test cases can be
run for single test device prepare by users.
However, it is being requested to support testing with multiple devices
prepared by users [1]. This request was made for atomic write tests for
md raid with four nvme devices. To run the test, users need to prepare
four suitable nvme devices and specify them in the blktests config file.
But blktests does not support such test with multiple devices.
[1]https://urldefense.com/v3/__https://lore.kernel.org/linux-
block/39c9f89a-6e6f-422f-88a2-3b2730b659a3@xxxxxxxxxx/__;!!
ACWV5N9M2RV99hQ!
O4lNHvPitDYTOvRaxHr03riTQ61P7uIwJtikwxnyMpSratty2qpugydf6IBdlg4sDIJTADlI2qq-Egssy7yXrkzqlWVN$
To support testing with multiple devices, I propose to extend blktests
framework. Currently, each test case is expected to implement test()
if the test case prepares devices, or test_device() to run the test for
the given single device. This series introduces another function
test_device_array(). It also introduces an associative array
TEST_CASE_DEV_ARRAY that users define in the config file. With this
,users can specify the multiple block devices that the test case with
test_device_array() uses.
The first patch is a preparation patch. The second patch introduces the
test_device_array() and the TEST_CASE_DEV_ARRAY. The third and the
fourth patches update the documents accordingly. The fifth patch adds
meta tests to confirm the functionality of the new feature.
As always, review comments will be appreciated. Thanks in advance.
Tested-by: John Garry <john.g.garry@xxxxxxxxxx>
