On Tue, Oct 22, 2024 at 04:23:29PM +0300, Sagi Grimberg wrote:
I agree. NVMe may have a unique need here, but it needs a tag from aI wonder if we should byte the bullet and not use a request for the
specific hctx while the context requesting it does not map according to
the hctx cpumap. It cannot use any other tag from any other hctx.
The reason is that the connect for a queue must be done from a tag that
belongs to the queue because nvme relies on it when it does resolution back
to
the request to the completion.
connect commands. We've already special cased the AEN command because
it was causing too many problems, and given all the pain so far connect
might also have hit that treshold.