| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 16 Jul 2010 15:44:57 +0300 From: Artem Bityutskiy <dedekind1@...il.com> To: Jens Axboe <axboe@...nel.dk> Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org Subject: [RFC][PATCH 01/16] writeback: do not self-wakeup From: Artem Bityutskiy <Artem.Bityutskiy@...ia.com> 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@...ia.com> --- 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-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists