From: Fengguang Wu <wfg@mail.ustc.edu.cn>
To: Chris Mason <chris.mason@oracle.com>
Cc: Andrew Morton <akpm@osdl.org>
Cc: David Chinner <dgc@sgi.com>
Cc: Michael Rubin <mrubin@google.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 1/3] writeback: introduce queue_dirty()
Date: Mon, 27 Aug 2007 19:21:53 +0800 [thread overview]
Message-ID: <388214369.33461@ustc.edu.cn> (raw)
Message-ID: <20070827113249.031094166@mail.ustc.edu.cn> (raw)
In-Reply-To: 20070827112152.816663278@mail.ustc.edu.cn
[-- Attachment #1: writeback-queue_dirty.patch --]
[-- Type: text/plain, Size: 1485 bytes --]
Introduce queue_dirty() to enqueue a newly dirtied inode.
It helps remove duplicate code.
Signed-off-by: Fengguang Wu <wfg@mail.ustc.edu.cn>
---
fs/fs-writeback.c | 21 +++++++++++++--------
1 file changed, 13 insertions(+), 8 deletions(-)
--- linux-2.6.23-rc3-mm1.orig/fs/fs-writeback.c
+++ linux-2.6.23-rc3-mm1/fs/fs-writeback.c
@@ -24,6 +24,15 @@
#include <linux/buffer_head.h>
#include "internal.h"
+/*
+ * Enqueue a newly dirtied inode.
+ */
+static void queue_dirty(struct inode *inode)
+{
+ inode->dirtied_when = jiffies;
+ list_move(&inode->i_list, &inode->i_sb->s_dirty);
+}
+
/**
* __mark_inode_dirty - internal function
* @inode: inode to mark
@@ -121,10 +130,8 @@ void __mark_inode_dirty(struct inode *in
* If the inode was already on s_dirty/s_io/s_more_io, don't
* reposition it (that would break s_dirty time-ordering).
*/
- if (!was_dirty) {
- inode->dirtied_when = jiffies;
- list_move(&inode->i_list, &sb->s_dirty);
- }
+ if (!was_dirty)
+ queue_dirty(inode);
}
out:
spin_unlock(&inode_lock);
@@ -466,10 +473,8 @@ int generic_sync_sb_inodes(struct super_
err = __writeback_single_inode(inode, wbc);
if (!ret)
ret = err;
- if (wbc->sync_mode == WB_SYNC_HOLD) {
- inode->dirtied_when = jiffies;
- list_move(&inode->i_list, &sb->s_dirty);
- }
+ if (wbc->sync_mode == WB_SYNC_HOLD)
+ queue_dirty(inode);
if (current_is_pdflush())
writeback_release(bdi);
if (wbc->pages_skipped != pages_skipped) {
--
next prev parent reply other threads:[~2007-08-27 11:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070827112152.816663278@mail.ustc.edu.cn>
2007-08-27 11:21 ` [PATCH 0/3] [RFC][PATCH] clustered writeback Fengguang Wu
2007-08-27 12:03 ` Arjan van de Ven
[not found] ` <20070827122738.GA6999@mail.ustc.edu.cn>
2007-08-27 12:27 ` Fengguang Wu
2007-08-27 12:43 ` Chris Mason
[not found] ` <20070827113249.031094166@mail.ustc.edu.cn>
2007-08-27 11:21 ` Fengguang Wu [this message]
[not found] ` <20070827113249.173435849@mail.ustc.edu.cn>
2007-08-27 11:21 ` [PATCH 2/3] writeback: introduce dirty_volatile_interval Fengguang Wu
[not found] ` <20070827113249.306814072@mail.ustc.edu.cn>
2007-08-27 11:21 ` [PATCH 3/3] writeback: writeback clustering by inode number Fengguang Wu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=388214369.33461@ustc.edu.cn \
--to=wfg@mail.ustc.edu.cn \
--cc=akpm@osdl.org \
--cc=chris.mason@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox