There isn't any reason to not support REQ_OP_ZONE_RESET_ALL given everything is actually handled in userspace, not mention it is pretty easy to support RESET_ALL. So enable REQ_OP_ZONE_RESET_ALL and let userspace handle it. Verified by 'tools/zbc_reset_zone -all /dev/ublkb0' in libzbc[1] with libublk-rs based ublk-zoned target prototype[2], follows command line for creating ublk-zoned: cargo run --example zoned -- add -1 1024 # add $dev_id $DEV_SIZE [1] https://github.com/westerndigitalcorporation/libzbc [2] https://github.com/ming1/libublk-rs/tree/zoned.v2
Showing the changes to include/uapi (1 of 2 files). Show all
Unified · Split
| @@ -245,6 +245,7 @@ struct ublksrv_ctrl_dev_info { · 244 unmodified lines | ||
| 245 | 245 | #define UBLK_IO_OP_ZONE_CLOSE 11 |
| 246 | 246 | #define UBLK_IO_OP_ZONE_FINISH 12 |
| 247 | 247 | #define UBLK_IO_OP_ZONE_APPEND 13 |
| 248 | +#define UBLK_IO_OP_ZONE_RESET_ALL 14 | |
| 248 | 249 | #define UBLK_IO_OP_ZONE_RESET 15 |
| 249 | 250 | /* |
| 250 | 251 | * Construct a zone report. The report request is carried in `struct |