From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: linux-fsdevel@vger.kernel.org
Cc: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Subject: [RFC] [PATCH] write-back: introduce a handy helper function
Date: Fri, 22 May 2009 21:38:28 +0300 [thread overview]
Message-ID: <20090522183828.29556.6658.sendpatchset@localhost.localdomain> (raw)
In-Reply-To: <20090522183820.29556.68026.sendpatchset@localhost.localdomain>
From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Subject: [PATCH] write-back: introduce a handy helper function
This patch is just a clean up and a preparation for the
following wb_timer patches. It introduces a helper
'setup_wb_timer()' function which sets up the periodic
write-back timer to the specified value. The code just
looks neater with this helper.
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
---
mm/page-writeback.c | 25 +++++++++++++++++++------
1 files changed, 19 insertions(+), 6 deletions(-)
diff --git a/mm/page-writeback.c b/mm/page-writeback.c
index bb553c3..f2496be 100644
--- a/mm/page-writeback.c
+++ b/mm/page-writeback.c
@@ -738,6 +738,21 @@ static DEFINE_TIMER(wb_timer, wb_timer_fn, 0, 0);
static DEFINE_TIMER(laptop_mode_wb_timer, laptop_timer_fn, 0, 0);
/*
+ * Setup the periodic write-back timer to expires at @expires jiffies. If
+ * @expires is zero, the timer is set up to the default interval.
+ */
+static void setup_wb_timer(unsigned long expires)
+{
+ if (!expires) {
+ /* Setup to the default wake-up period value */
+ expires = jiffies;
+ expires += msecs_to_jiffies(dirty_writeback_interval * 10);
+ }
+
+ mod_timer(&wb_timer, expires);
+}
+
+/*
* Periodic writeback of "old" data.
*
* Define "old": the first time one of an inode's pages is dirtied, we mark the
@@ -792,7 +807,7 @@ static void wb_kupdate(unsigned long arg)
if (time_before(next_jif, jiffies + HZ))
next_jif = jiffies + HZ;
if (dirty_writeback_interval)
- mod_timer(&wb_timer, next_jif);
+ setup_wb_timer(next_jif);
}
/*
@@ -803,8 +818,7 @@ int dirty_writeback_centisecs_handler(ctl_table *table, int write,
{
proc_dointvec(table, write, file, buffer, length, ppos);
if (dirty_writeback_interval)
- mod_timer(&wb_timer, jiffies +
- msecs_to_jiffies(dirty_writeback_interval * 10));
+ setup_wb_timer(0);
else
del_timer(&wb_timer);
return 0;
@@ -813,7 +827,7 @@ int dirty_writeback_centisecs_handler(ctl_table *table, int write,
static void wb_timer_fn(unsigned long unused)
{
if (pdflush_operation(wb_kupdate, 0) < 0)
- mod_timer(&wb_timer, jiffies + HZ); /* delay 1 second */
+ setup_wb_timer( jiffies + HZ); /* delay 1 second */
}
static void laptop_flush(unsigned long unused)
@@ -906,8 +920,7 @@ void __init page_writeback_init(void)
{
int shift;
- mod_timer(&wb_timer,
- jiffies + msecs_to_jiffies(dirty_writeback_interval * 10));
+ setup_wb_timer(0);
writeback_set_ratelimit();
register_cpu_notifier(&ratelimit_nb);
--
1.6.0.6
next prev parent reply other threads:[~2009-05-22 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 18:38 [RFC] few hacks to optimize write-back Artem Bityutskiy
2009-05-22 18:38 ` Artem Bityutskiy [this message]
2009-05-22 18:38 ` [RFC] [PATCH] write-back: do not wake up unnecessarily Artem Bityutskiy
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=20090522183828.29556.6658.sendpatchset@localhost.localdomain \
--to=artem.bityutskiy@nokia.com \
--cc=linux-fsdevel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).