Re: [PATCH 2/2] blk-mq: don't use WORK_CPU_UNBOUND

2017-08-21 Thread Tejun Heo
On Mon, Aug 21, 2017 at 03:49:51PM +0200, Laurent Vivier wrote: > cpumask is the list of CPUs present when the queue is built. > If a new CPU is hotplugged, this list is not updated, > and when the scheduler asks for a CPU id, blk_mq_hctx_next_cpu() > can return WORK_CPU_UNBOUND. > And in this

Re: [PATCH 2/2] blk-mq: don't use WORK_CPU_UNBOUND

2017-08-21 Thread Tejun Heo
On Mon, Aug 21, 2017 at 03:49:51PM +0200, Laurent Vivier wrote: > cpumask is the list of CPUs present when the queue is built. > If a new CPU is hotplugged, this list is not updated, > and when the scheduler asks for a CPU id, blk_mq_hctx_next_cpu() > can return WORK_CPU_UNBOUND. > And in this

[PATCH 2/2] blk-mq: don't use WORK_CPU_UNBOUND

2017-08-21 Thread Laurent Vivier
cpumask is the list of CPUs present when the queue is built. If a new CPU is hotplugged, this list is not updated, and when the scheduler asks for a CPU id, blk_mq_hctx_next_cpu() can return WORK_CPU_UNBOUND. And in this case _blk_mq_run_hw_queue() can be executed by the new CPU (that is not

[PATCH 2/2] blk-mq: don't use WORK_CPU_UNBOUND

2017-08-21 Thread Laurent Vivier
cpumask is the list of CPUs present when the queue is built. If a new CPU is hotplugged, this list is not updated, and when the scheduler asks for a CPU id, blk_mq_hctx_next_cpu() can return WORK_CPU_UNBOUND. And in this case _blk_mq_run_hw_queue() can be executed by the new CPU (that is not