Re: [PATCH V5] blk-mq: don't schedule block kworker on isolated CPUs

[Jens Axboe]

On Fri, 22 Mar 2024 10:12:44 +0800, Ming Lei wrote:
> Kernel parameter of `isolcpus=` or 'nohz_full=' are used to isolate CPUs
> for specific task, and it isn't expected to let block IO disturb these CPUs.
> blk-mq kworker shouldn't be scheduled on isolated CPUs. Also if isolated
> CPUs is run for blk-mq kworker, long block IO latency can be caused.
> 
> Kernel workqueue only respects CPU isolation for WQ_UNBOUND, for bound
> WQ, the responsibility is on user because CPU is specified as WQ API
> parameter, such as mod_delayed_work_on(cpu), queue_delayed_work_on(cpu)
> and queue_work_on(cpu).
> 
> [...]

Applied, thanks!

[1/1] blk-mq: don't schedule block kworker on isolated CPUs
      commit: 5f27f3d892743312fce237958a4194859ef93d69

Best regards,
-- 
Jens Axboe