In commit 53493c1f836f ("hw/nvme: cap MDTS value for internal
limitation"), the max value of MDTS was restricted to ensure that the
device will not report internal device errors when hitting the internal
IOV_MAX limit of the block layer.

This series attempts to lift the IOV_MAX restrictions, by splitting I/O
in the dma helpers.

Signed-off-by: Klaus Jensen <k.jensen@samsung.com>
---
Klaus Jensen (2):
      dma-helpers: lift IOV_MAX limit
      hw/nvme: allow MDTS above 9

 hw/nvme/ctrl.c       | 17 ++---------------
 system/dma-helpers.c |  5 ++++-
 2 files changed, 6 insertions(+), 16 deletions(-)
---
base-commit: 559919ce54927d59b215a4665eda7ab6118a48aa
change-id: 20260317-lift-iovmax-dma-limit-5266d83d0820

Best regards,
-- 
Klaus Jensen <k.jensen@samsung.com>

On Tue, Mar 17, 2026 at 09:48:56AM +0100, Klaus Jensen wrote:
> In commit 53493c1f836f ("hw/nvme: cap MDTS value for internal
> limitation"), the max value of MDTS was restricted to ensure that the
> device will not report internal device errors when hitting the internal
> IOV_MAX limit of the block layer.
> 
> This series attempts to lift the IOV_MAX restrictions, by splitting I/O
> in the dma helpers.

Nice, this was simpler than I thought! Looks good to me:

Acked-by: Keith Busch <kbusch@kernel.org>