Gabriel Krisman Bertazi writes:
> My one concern about this patch is if remapping an arbitrary queue to
> hctx_0 could result in outstanding requests getting submitted to the
> wrong hctx. I couldn't observe this happening during tests, but I'm not
> entirely sure it'll never happen. I believe
In blk_mq_map_swqueue, there is a memory optimization that frees the
tags of a queue that has gone unmapped. Later, if that hctx is remapped
after another topology change, the tags need to be reallocated.
If this allocation fails, a simple WARN_ON triggers, but the block layer
ends up with an act
2 matches
Mail list logo
