Skip to content

workqueue: Destroy workers in idle_cull_fn().

Lai Jiangshan lkml 1 version Applied

Status from this message: Applied to wq/for-6.11.

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest4 patches 10 repliesApplied

Patches in v1 Applied

#Subject and filesSizeRepliesApplied
1/4workqueue: Reap workers via kthread_stop() and remove detach_completionkernel/workqueue.c+19 -169 replies
2/4workqueue: Don't bind the rescuer in the last working cpukernel/workqueue.c+12 -120 replies
3/4workqueue: Detach workers directly in idle_cull_fn()kernel/workqueue.c+19 -260 replies
4/4workqueue: Remove useless pool->dying_workerskernel/workqueue.c+0 -30 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/4] workqueue: Destroy workers in idle_cull_fn().

From: Lai Jiangshan <[email protected]>

After e02b93124855("workqueue: Unbind kworkers before sending them to exit()"), the code to kick off the destruction of workers is now in a process context (idle_cull_fn()), more destruction code can also be moved to the said process context to simplify the destroying.

Cc Tejun Heo <[email protected]>
Cc Valentin Schneider <[email protected]>

Lai Jiangshan (4):
workqueue: Reap workers via kthread_stop() and remove
detach_completion
workqueue: Don't bind the rescuer in the last working cpu
workqueue: Detach workers directly in idle_cull_fn()
workqueue: Remove useless pool->dying_workers

 kernel/workqueue.c | 87 +++++++++++++++++++++-------------------------
 1 file changed, 40 insertions(+), 47 deletions(-)
Signature · 1 line
2.19.1.6.gb485710b