Re: [PATCH] blk-mq: Always schedule hctx->next_cpu

2016-10-28 Thread Jens Axboe
On 09/27/2016 09:24 PM, Gabriel Krisman Bertazi wrote: Commit 0e87e58bf60e ("blk-mq: improve warning for running a queue on the wrong CPU") attempts to avoid triggering the WARN_ON in __blk_mq_run_hw_queue when the expected CPU is dead. Problem is, in the last batch execution before round

[PATCH] blk-mq: Always schedule hctx->next_cpu

2016-09-27 Thread Gabriel Krisman Bertazi
Commit 0e87e58bf60e ("blk-mq: improve warning for running a queue on the wrong CPU") attempts to avoid triggering the WARN_ON in __blk_mq_run_hw_queue when the expected CPU is dead. Problem is, in the last batch execution before round robin, blk_mq_hctx_next_cpu can schedule a dead CPU and also