No functional change. There are two worker pools for each cpu in current implementation(one for normal work items and the other for high priority ones).
Signed-off-by: Libin <huawei.li...@huawei.com> --- kernel/workqueue.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/kernel/workqueue.c b/kernel/workqueue.c index 7f5d4be..26644ce 100644 --- a/kernel/workqueue.c +++ b/kernel/workqueue.c @@ -16,9 +16,10 @@ * * This is the generic async execution mechanism. Work items as are * executed in process context. The worker pool is shared and - * automatically managed. There is one worker pool for each CPU and - * one extra for works which are better served by workers which are - * not bound to any specific CPU. + * automatically managed. There are two worker pools for each CPU(one + * for normal work items and the other for high priority ones) and + * some extra pools for workqueues which are not bound to any specific + * CPU - the number of these backing pools is dynamic. * * Please read Documentation/workqueue.txt for details. */ -- 1.8.2.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
