From: Fengguang Wu <wfg@mail.ustc.edu.cn>
To: Chris Mason <chris.mason@oracle.com>
Cc: Andrew Morton <akpm@osdl.org>, Jens Axboe <jens.axboe@oracle.com>,
David Chinner <dgc@sgi.com>, Ken Chen <kenchen@google.com>,
Michael Rubin <mrubin@google.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 2/3] writeback: introduce dirty_volatile_interval
Date: Mon, 27 Aug 2007 19:21:54 +0800 [thread overview]
Message-ID: <388214369.67692@ustc.edu.cn> (raw)
Message-ID: <20070827113249.173435849@mail.ustc.edu.cn> (raw)
In-Reply-To: 20070827112152.816663278@mail.ustc.edu.cn
[-- Attachment #1: writeback-young_protect_interval.patch --]
[-- Type: text/plain, Size: 2004 bytes --]
Introduce dirty_volatile_interval for the minimal dirty time.
Inodes dirtied less than dirty_volatile_interval will not be
considered for syncing by kupdate-style writeback.
This new parameter will be used in clustered writeback.
The old dirty_expire_interval is still(but less) respected.
Cc: Chris Mason <chris.mason@oracle.com>
Cc: Jens Axboe <jens.axboe@oracle.com>
Cc: David Chinner <dgc@sgi.com>
Cc: Ken Chen <kenchen@google.com>
Cc: Michael Rubin <mrubin@google.com>
Cc: Andrew Morton <akpm@osdl.org>
Signed-off-by: Fengguang Wu <wfg@mail.ustc.edu.cn>
---
include/linux/writeback.h | 1 +
kernel/sysctl.c | 7 +++++++
mm/page-writeback.c | 5 +++++
3 files changed, 13 insertions(+)
--- linux-2.6.23-rc3-mm1.orig/include/linux/writeback.h
+++ linux-2.6.23-rc3-mm1/include/linux/writeback.h
@@ -101,6 +101,7 @@ extern int dirty_background_ratio;
extern int vm_dirty_ratio;
extern int dirty_writeback_interval;
extern int dirty_expire_interval;
+extern int dirty_volatile_interval;
extern int block_dump;
extern int laptop_mode;
--- linux-2.6.23-rc3-mm1.orig/mm/page-writeback.c
+++ linux-2.6.23-rc3-mm1/mm/page-writeback.c
@@ -85,6 +85,11 @@ int dirty_writeback_interval = 5 * HZ;
int dirty_expire_interval = 30 * HZ;
/*
+ * The shortest number of jiffies for which data should remain dirty
+ */
+int dirty_volatile_interval = 5 * HZ;
+
+/*
* Flag that makes the machine dump writes/reads and block dirtyings.
*/
int block_dump;
--- linux-2.6.23-rc3-mm1.orig/kernel/sysctl.c
+++ linux-2.6.23-rc3-mm1/kernel/sysctl.c
@@ -837,6 +837,13 @@ static struct ctl_table vm_table[] = {
.proc_handler = &proc_dointvec_userhz_jiffies,
},
{
+ .procname = "dirty_volatile_centisecs",
+ .data = &dirty_volatile_interval,
+ .maxlen = sizeof(dirty_volatile_interval),
+ .mode = 0644,
+ .proc_handler = &proc_dointvec_userhz_jiffies,
+ },
+ {
.ctl_name = VM_NR_PDFLUSH_THREADS,
.procname = "nr_pdflush_threads",
.data = &nr_pdflush_threads,
--
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 ` [PATCH 1/3] writeback: introduce queue_dirty() Fengguang Wu
[not found] ` <20070827113249.173435849@mail.ustc.edu.cn>
2007-08-27 11:21 ` Fengguang Wu [this message]
[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.67692@ustc.edu.cn \
--to=wfg@mail.ustc.edu.cn \
--cc=akpm@osdl.org \
--cc=chris.mason@oracle.com \
--cc=dgc@sgi.com \
--cc=jens.axboe@oracle.com \
--cc=kenchen@google.com \
--cc=mrubin@google.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