On Wed, Apr 03, 2024 at 04:17:54PM +0200, Hannes Reinecke wrote: > Hi all, > > there had been several attempts to implement a latency-based I/O > scheduler for native nvme multipath, all of which had its issues. > > So time to start afresh, this time using the QoS framework > already present in the block layer. > It consists of two parts: > - a new 'blk-nlatency' QoS module, which is just a simple per-node > latency tracker > - a 'latency' nvme I/O policy Whatever happened with the io-depth based path selector? That should naturally align with the lower latency path, and that metric is cheaper to track.
