[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180523232508.GA1351649@devbig577.frc2.facebook.com>
Date: Wed, 23 May 2018 16:25:08 -0700
From: Tejun Heo <tj@...nel.org>
To: Jens Axboe <axboe@...nel.dk>
Cc: linux-kernel@...r.kernel.org,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Jan Kara <jack@...e.com>,
Andrew Morton <akpm@...ux-foundation.org>, kernel-team@...com,
Rik van Riel <riel@...riel.com>
Subject: [PATCH] bdi: Increase the concurrecy level of cgwb_release_wq
cgwb_release_wq was added to isolate and limit the concurrency level
of cgwb release work items. The max concurrency was set to 1 per CPU
but we do want some level of concurrency as otherwise it ends up
calling, through bdi_unregister(), synchronize_sched_expedited()
back-to-back for each release work item.
Let's allow them to bunch up a bit.
Signed-off-by: Tejun Heo <tj@...nel.org>
Suggested-by: Rik van Riel <riel@...riel.com>
---
mm/backing-dev.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/mm/backing-dev.c b/mm/backing-dev.c
index 8fe3ebd..f9a2268 100644
--- a/mm/backing-dev.c
+++ b/mm/backing-dev.c
@@ -790,9 +790,10 @@ static int __init cgwb_init(void)
/*
* There can be many concurrent release work items overwhelming
* system_wq. Put them in a separate wq and limit concurrency.
- * There's no point in executing many of these in parallel.
+ * Allow some level of concurrency so that we can batch on
+ * synchronize_rcu_expedited() calls in bdi_unregister().
*/
- cgwb_release_wq = alloc_workqueue("cgwb_release", 0, 1);
+ cgwb_release_wq = alloc_workqueue("cgwb_release", 0, 16);
if (!cgwb_release_wq)
return -ENOMEM;
Powered by blists - more mailing lists