Messages in this thread | | | Date | Tue, 22 Feb 2022 07:29:50 -1000 | From | Tejun Heo <> | Subject | Re: [PATCH] workqueue: Use private WQ for schedule_on_each_cpu() API |
| |
On Mon, Feb 21, 2022 at 07:38:09PM +0900, Tetsuo Handa wrote: > Since schedule_on_each_cpu() calls schedule_work_on() and flush_work(), > we should avoid using system_wq in order to avoid unexpected locking > dependency.
I don't get it. schedule_on_each_cpu() is flushing each work item and thus shouldn't need its own flushing domain. What's this change for?
Thanks.
-- tejun
| |