[PATCH V4 6/9] nvme: use per controller timeout waits over depending on global default

Christoph Hellwig hch at lst.de
Mon May 11 05:32:11 PDT 2026


On Mon, May 11, 2026 at 01:42:47PM +0200, Maurizio Lombardi wrote:
> On Mon May 11, 2026 at 10:10 AM CEST, Christoph Hellwig wrote:
> > On Fri, May 08, 2026 at 03:33:32PM +0200, Maurizio Lombardi wrote:
> >> Instead of passing NVME_IO_TIMEOUT as a parameter with every call to
> >> nvme_wait_freeze_timeout, use the controller's preferred timeout.
> >
> > This should probably go very early in the series before even adding
> > configurable timeouts as it just drops a pointless paramter.
> 
> It drops the parameter but uses the timeout value stored in
> ctrl->io_timeout, so it actually depends on the patch introducing
> the per-controller io_timeout.

Well, switch to hardcoded NVME_IO_TIMEOUT early, and then replace it
with the variable timeout like the other instances of NVME_IO_TIMEOUT.

> 
> Maurizio
---end quoted text---



More information about the Linux-nvme mailing list