From: Artem Bityutskiy <Artem.Bityutskiy@xxxxxxxxx> The bdi forker thread wakes up itself via 'bdi_add_to_pending()'. And the thread is the only user of 'bdi_add_to_pending()'. Thus, we can safely zap the unneeded 'wake_up_process()' call. Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@xxxxxxxxx> --- mm/backing-dev.c | 6 ------ 1 files changed, 0 insertions(+), 6 deletions(-) diff --git a/mm/backing-dev.c b/mm/backing-dev.c index ac78a33..ff5669a 100644 --- a/mm/backing-dev.c +++ b/mm/backing-dev.c @@ -421,12 +421,6 @@ static void bdi_add_to_pending(struct rcu_head *head) spin_lock(&bdi_lock); list_add_tail(&bdi->bdi_list, &bdi_pending_list); spin_unlock(&bdi_lock); - - /* - * We are now on the pending list, wake up bdi_forker_task() - * to finish the job and add us back to the active bdi_list - */ - wake_up_process(default_backing_dev_info.wb.task); } /* -- 1.7.1.1 -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
