You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
throtl: support test with both null_blk and scsi_debug in a single run
The previous commit introduced the global variable throtl_blkdev_type to
specify the type of block device for the throtl group. However, users
need to run tests twice modifying the variable's value each time to test
against both device types null_blk and scsi_debug. This workflow is
cumbersome.
To run the throtl group for both null_blk and scsi_debug in a single
run, introduce the global variable THROTL_BLKDEV_TYPES instead of
throtl_blkdev_type. When THROTL_BLKDEV_TYPES is set to 'nullb sdebug',
the blktests framework executes each test case in the throtl group for
both null_blk and scsi_debug sequentially. For this purpose, introduce
the helper function _set_throtl_blkdev_type() and call it in
set_conditions() hooks of the test cases.
Each of the two command lines below runs the throtl group with both
null_blk and scsi_debug. Please note that the default value of
THROTL_BLKDEV_TYPES is 'nullb sdebug'.
$ sudo bash -c "./check throtl/"
$ sudo bash -c "THROTL_BLKDEV_TYPES='nullb sdebug' ./check throtl/"
Each of the command lines below runs the throtl group only for null_blk
or scsi_debug, respectively.
$ sudo bash -c "THROTL_BLKDEV_TYPES='nullb' ./check throtl/"
$ sudo bash -c "THROTL_BLKDEV_TYPES='sdebug' ./check throtl/"
Reviewed-by: Chaitanya Kulkarni <[email protected]>
Signed-off-by: Shin'ichiro Kawasaki <[email protected]>
0 commit comments