On Thu, 15 Feb 2024 20:48:09 +0530, Ankit Kumar wrote:
> NVMe specification allow multiple ranges for the dataset management
> command. The block ioctl only accepts a single entry for trim, but
> with nvme character device we can send multiple ranges.
>
> The first patch in this series adds an option num_range to send multiple
> range per trim request. This will only work if the data direction is
> solely trim i.e. trim or randtrim.
>
> [...]
Applied, thanks!
[1/3] trim: add support for multiple ranges
commit: b3251e31bae2c2ec7c8db0e7e7511eb03b8b0190
[2/3] engines/nvme: pass offset and len instead of io_u
commit: 0d610785a8072eba146dd05f2928a1a89da49bd5
[3/3] engines/io_uring: add multi range dsm support
commit: 5d4ee0de9d6afaa74c7c15c3d4f210a06d4e2139
Best regards,
--
Jens Axboe
