Hi,
This is v2 as Paul's comments, please take them if any.
Cheers,
Zumeng
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
From: Lai Jiangshan la...@cn.fujitsu.com
commit 9625ab1727743f6a164df26b7b1eeeced7380b42 upstream
worker_idr is highly bound to managers and is always/only accessed in manager
lock context. So we don't need pool-lock for it.
Signed-off-by: Lai Jiangshan la...@cn.fujitsu.com
Signed-off-by: Tejun
From: Lai Jiangshan la...@cn.fujitsu.com
commit 60f5a4bcf852b5dec698b08cd34efc302ea72f2b upstream
worker destruction includes these parts of code:
adjust pool's stats
remove the worker from idle list
detach the worker from the pool
kthread_stop() to wait for the
From: Lai Jiangshan la...@cn.fujitsu.com
commit 7cda9aae0596d871a8d7a6888d7b447c60e5ab30 upstream
We no longer iterate workers via worker_idr and worker_idr is used
only for allocating/freeing ID, so we can convert it to worker_ida.
By using ida_simple_get/remove(), worker_ida doesn't require