[PATCH 1/2] nvme: multipath: round-robin: fix logic for non-optimized paths

[Sagi Grimberg]

>>> Handle the special case where we have exactly one optimized path,
>>> which we should keep using in this case. Also, use the next
>>> non-optimized path, not the last one.
>>
>> Not sure I understand, does this patch also use nonopt paths if we
>> have a single opt path?
> 
> Indeed, the latter change should be removed from this patch.

Why should we even do this? we have a clear indication from the
controller on ns access. If we have a optimized path we should never
select any non-optimized path.

What if a non-optimized path has a 50x higher access latency? it's just
wrong to use this path...