From: Jan Kara Subject: [PATCH 08/14] writeback: Schedule future writeback if bdi (not wb) has dirty inodes Date: Fri, 1 Aug 2014 00:00:47 +0200 Message-ID: <1406844053-25982-9-git-send-email-jack@suse.cz> References: <1406844053-25982-1-git-send-email-jack@suse.cz> Cc: OGAWA Hirofumi , Wu Fengguang , Jan Kara To: linux-fsdevel@vger.kernel.org Return-path: Received: from cantor2.suse.de ([195.135.220.15]:42516 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750945AbaGaWBQ (ORCPT ); Thu, 31 Jul 2014 18:01:16 -0400 In-Reply-To: <1406844053-25982-1-git-send-email-jack@suse.cz> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: bdi_writeback_workfn() uses wb_has_dirty_io() to determine whether it should schedule writeback work in future. With per-sb dirty tracking we are going to have more dirty lists for bdi so we have to use bdi_has_dirty_io() which will properly iterate all of the lists. Signed-off-by: Jan Kara --- fs/fs-writeback.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c index 4247e1f7cb03..c8806c81e37c 100644 --- a/fs/fs-writeback.c +++ b/fs/fs-writeback.c @@ -957,7 +957,7 @@ void bdi_writeback_workfn(struct work_struct *work) if (!list_empty(&bdi->work_list)) mod_delayed_work(bdi_wq, &bdi->dwork, 0); - else if (wb_has_dirty_io(wb) && dirty_writeback_interval) + else if (bdi_has_dirty_io(bdi) && dirty_writeback_interval) bdi_wakeup_thread_delayed(bdi); current->flags &= ~PF_SWAPWRITE; -- 1.8.1.4