From: chenqiwu <chenqiwu@xxxxxxxxxx> There is a potential starvation that the number of delayed fput works increase rapidly if task exit storm or fs unmount issue happens. Since the delayed fput works are expected to be executed as soon as possible. The commonly accepted wisdom that the measurements of scheduling works via the unbound workqueue show lowered worst-case latency responses of up to 5x over bound workqueue. Work items queued to an unbound wq are not bound to any specific CPU, not concurrency managed. All queued works are executed immediately as long as max_active limit is not reached and resources are available. Signed-off-by: chenqiwu <chenqiwu@xxxxxxxxxx> --- fs/file_table.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/fs/file_table.c b/fs/file_table.c index 30d55c9..472ad92 100644 --- a/fs/file_table.c +++ b/fs/file_table.c @@ -348,7 +348,8 @@ void fput_many(struct file *file, unsigned int refs) } if (llist_add(&file->f_u.fu_llist, &delayed_fput_list)) - schedule_delayed_work(&delayed_fput_work, 1); + queue_delayed_work(system_unbound_wq, + &delayed_fput_work, 1); } } -- 1.9.1
