From: Fengguang Wu Subject: [PATCH 12/13] writeback: remove redirty_tail() Date: Tue, 15 Jan 2008 20:36:49 +0800 Message-ID: <400401294.78786@ustc.edu.cn> References: <20080115123637.518924046@mail.ustc.edu.cn> Cc: Michael Rubin , Peter Zijlstra To: Andrew Morton Return-path: Received: from smtp.ustc.edu.cn ([202.38.64.16]:48048 "HELO ustc.edu.cn" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with SMTP id S1751384AbYAOMsI (ORCPT ); Tue, 15 Jan 2008 07:48:08 -0500 Message-Id: <20080115124802.624775214@mail.ustc.edu.cn> Cc: linux-fsdevel@vger.kernel.org Cc: linux-kernel@vger.kernel.org Content-Disposition: inline; filename=writeback-remove-redirty_tail.patch Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Remove redirty_tail(). It's no longer used. Cc: Michael Rubin Cc: Peter Zijlstra Signed-off-by: Fengguang Wu --- fs/fs-writeback.c | 24 ------------------------ 1 files changed, 24 deletions(-) --- linux-mm.orig/fs/fs-writeback.c +++ linux-mm/fs/fs-writeback.c @@ -148,30 +148,6 @@ static int write_inode(struct inode *ino } /* - * Redirty an inode: set its when-it-was dirtied timestamp and move it to the - * furthest end of its superblock's dirty-inode list. - * - * Before stamping the inode's ->dirtied_when, we check to see whether it is - * already the most-recently-dirtied inode on the s_dirty list. If that is - * the case then the inode must have been redirtied while it was being written - * out and we don't reset its dirtied_when. - */ -static void redirty_tail(struct inode *inode) -{ - struct super_block *sb = inode->i_sb; - - if (!list_empty(&sb->s_dirty)) { - struct inode *tail_inode; - - tail_inode = list_entry(sb->s_dirty.next, struct inode, i_list); - if (!time_after_eq(inode->dirtied_when, - tail_inode->dirtied_when)) - inode->dirtied_when = jiffies; - } - list_move(&inode->i_list, &sb->s_dirty); -} - -/* * requeue inode for re-scanning after sb->s_io list is exhausted. */ static void requeue_io(struct inode *inode) --