From: Wu Fengguang <fengguang.wu@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jan Kara <jack@suse.cz>, larry <lantianyu1986@gmail.com>,
Wu Fengguang <fengguang.wu@intel.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Dave Chinner <david@fromorbit.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>
Cc: Chris Mason <chris.mason@oracle.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Mel Gorman <mel@csn.ul.ie>
Cc: Rik van Riel <riel@redhat.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Greg Thelen <gthelen@google.com>
Cc: Minchan Kim <minchan.kim@gmail.com>
Cc: Vivek Goyal <vgoyal@redhat.com>
Cc: Andrea Righi <arighi@develer.com>
Cc: Balbir Singh <balbir@linux.vnet.ibm.com>
Cc: linux-mm <linux-mm@kvack.org>
Cc: <linux-fsdevel@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 04/12] writeback: smoothed global/bdi dirty pages
Date: Sat, 16 Apr 2011 21:25:50 +0800 [thread overview]
Message-ID: <20110416134332.918936130@intel.com> (raw)
In-Reply-To: 20110416132546.765212221@intel.com
[-- Attachment #1: writeback-smooth-dirty.patch --]
[-- Type: text/plain, Size: 4037 bytes --]
Maintain a smoothed version of dirty pages for use in the throttle
bandwidth calculations.
default_backing_dev_info.avg_dirty holds the smoothed global dirty
pages.
The calculation favors smoothness rather than accuracy. It's non-sense
trying to track a much fluctuated value "accurately". And its users
don't really rely on it being accurate.
CC: larry <lantianyu1986@gmail.com>
Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
---
include/linux/backing-dev.h | 2 +
mm/backing-dev.c | 3 +
mm/page-writeback.c | 66 ++++++++++++++++++++++++++++++++++
3 files changed, 71 insertions(+)
--- linux-next.orig/mm/page-writeback.c 2011-04-13 17:18:12.000000000 +0800
+++ linux-next/mm/page-writeback.c 2011-04-13 17:18:12.000000000 +0800
@@ -471,6 +471,64 @@ unsigned long bdi_dirty_limit(struct bac
return bdi_dirty;
}
+static void bdi_update_dirty_smooth(struct backing_dev_info *bdi,
+ unsigned long dirty)
+{
+ unsigned long avg = bdi->avg_dirty;
+ unsigned long old = bdi->old_dirty;
+
+ if (unlikely(!avg)) {
+ avg = dirty;
+ goto update;
+ }
+
+ /*
+ * dirty pages are departing upwards, follow up
+ */
+ if (avg < old && old <= dirty) {
+ avg += (old - avg) >> 2;
+ goto update;
+ }
+
+ /*
+ * dirty pages are departing downwards, follow down
+ */
+ if (avg > old && old >= dirty) {
+ avg -= (avg - old) >> 2;
+ goto update;
+ }
+
+ /*
+ * This can filter out one half unnecessary updates when bdi_dirty is
+ * fluctuating around the balance point, and is most effective on XFS,
+ * whose pattern is
+ * .
+ * [.] dirty [-] avg . .
+ * . .
+ * . . . . . .
+ * --------------------------------------- . .
+ * . . . . . .
+ * . . . . . .
+ * . . . . . .
+ * . . . . . .
+ * . . . .
+ * . . . . (fluctuated)
+ * . . . .
+ * . . . .
+ *
+ * @avg will remain flat at the cost of being biased towards high. In
+ * practice the error tend to be much smaller: thanks to more coarse
+ * grained fluctuations, @avg becomes the real average number for the
+ * last two rising lines of @dirty.
+ */
+ goto out;
+
+update:
+ bdi->avg_dirty = avg;
+out:
+ bdi->old_dirty = dirty;
+}
+
static void __bdi_update_write_bandwidth(struct backing_dev_info *bdi,
unsigned long elapsed,
unsigned long written)
@@ -535,6 +593,14 @@ void bdi_update_bandwidth(struct backing
if (elapsed <= HZ / 5)
goto unlock;
+ if (thresh &&
+ now - default_backing_dev_info.bw_time_stamp >= HZ / 5) {
+ bdi_update_dirty_smooth(&default_backing_dev_info, dirty);
+ default_backing_dev_info.bw_time_stamp = now;
+ }
+ if (thresh) {
+ bdi_update_dirty_smooth(bdi, bdi_dirty);
+ }
__bdi_update_write_bandwidth(bdi, elapsed, written);
snapshot:
--- linux-next.orig/include/linux/backing-dev.h 2011-04-13 17:18:12.000000000 +0800
+++ linux-next/include/linux/backing-dev.h 2011-04-13 17:18:12.000000000 +0800
@@ -77,6 +77,8 @@ struct backing_dev_info {
unsigned long written_stamp;
unsigned long write_bandwidth;
unsigned long avg_write_bandwidth;
+ unsigned long avg_dirty;
+ unsigned long old_dirty;
struct prop_local_percpu completions;
int dirty_exceeded;
--- linux-next.orig/mm/backing-dev.c 2011-04-13 17:18:12.000000000 +0800
+++ linux-next/mm/backing-dev.c 2011-04-13 17:18:12.000000000 +0800
@@ -669,6 +669,9 @@ int bdi_init(struct backing_dev_info *bd
bdi->write_bandwidth = INIT_BW;
bdi->avg_write_bandwidth = INIT_BW;
+ bdi->avg_dirty = 0;
+ bdi->old_dirty = 0;
+
err = prop_local_init_percpu(&bdi->completions);
if (err) {
WARNING: multiple messages have this Message-ID (diff)
From: Wu Fengguang <fengguang.wu@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jan Kara <jack@suse.cz>, larry <lantianyu1986@gmail.com>,
Wu Fengguang <fengguang.wu@intel.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Dave Chinner <david@fromorbit.com>
Cc: Theodore Ts'o <tytso@mit.edu>
Cc: Chris Mason <chris.mason@oracle.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Mel Gorman <mel@csn.ul.ie>
Cc: Rik van Riel <riel@redhat.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Greg Thelen <gthelen@google.com>
Cc: Minchan Kim <minchan.kim@gmail.com>
Cc: Vivek Goyal <vgoyal@redhat.com>
Cc: Andrea Righi <arighi@develer.com>
Cc: Balbir Singh <balbir@linux.vnet.ibm.com>
Cc: linux-mm <linux-mm@kvack.org>
Cc: <linux-fsdevel@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 04/12] writeback: smoothed global/bdi dirty pages
Date: Sat, 16 Apr 2011 21:25:50 +0800 [thread overview]
Message-ID: <20110416134332.918936130@intel.com> (raw)
In-Reply-To: 20110416132546.765212221@intel.com
[-- Attachment #1: writeback-smooth-dirty.patch --]
[-- Type: text/plain, Size: 4340 bytes --]
Maintain a smoothed version of dirty pages for use in the throttle
bandwidth calculations.
default_backing_dev_info.avg_dirty holds the smoothed global dirty
pages.
The calculation favors smoothness rather than accuracy. It's non-sense
trying to track a much fluctuated value "accurately". And its users
don't really rely on it being accurate.
CC: larry <lantianyu1986@gmail.com>
Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
---
include/linux/backing-dev.h | 2 +
mm/backing-dev.c | 3 +
mm/page-writeback.c | 66 ++++++++++++++++++++++++++++++++++
3 files changed, 71 insertions(+)
--- linux-next.orig/mm/page-writeback.c 2011-04-13 17:18:12.000000000 +0800
+++ linux-next/mm/page-writeback.c 2011-04-13 17:18:12.000000000 +0800
@@ -471,6 +471,64 @@ unsigned long bdi_dirty_limit(struct bac
return bdi_dirty;
}
+static void bdi_update_dirty_smooth(struct backing_dev_info *bdi,
+ unsigned long dirty)
+{
+ unsigned long avg = bdi->avg_dirty;
+ unsigned long old = bdi->old_dirty;
+
+ if (unlikely(!avg)) {
+ avg = dirty;
+ goto update;
+ }
+
+ /*
+ * dirty pages are departing upwards, follow up
+ */
+ if (avg < old && old <= dirty) {
+ avg += (old - avg) >> 2;
+ goto update;
+ }
+
+ /*
+ * dirty pages are departing downwards, follow down
+ */
+ if (avg > old && old >= dirty) {
+ avg -= (avg - old) >> 2;
+ goto update;
+ }
+
+ /*
+ * This can filter out one half unnecessary updates when bdi_dirty is
+ * fluctuating around the balance point, and is most effective on XFS,
+ * whose pattern is
+ * .
+ * [.] dirty [-] avg . .
+ * . .
+ * . . . . . .
+ * --------------------------------------- . .
+ * . . . . . .
+ * . . . . . .
+ * . . . . . .
+ * . . . . . .
+ * . . . .
+ * . . . . (fluctuated)
+ * . . . .
+ * . . . .
+ *
+ * @avg will remain flat at the cost of being biased towards high. In
+ * practice the error tend to be much smaller: thanks to more coarse
+ * grained fluctuations, @avg becomes the real average number for the
+ * last two rising lines of @dirty.
+ */
+ goto out;
+
+update:
+ bdi->avg_dirty = avg;
+out:
+ bdi->old_dirty = dirty;
+}
+
static void __bdi_update_write_bandwidth(struct backing_dev_info *bdi,
unsigned long elapsed,
unsigned long written)
@@ -535,6 +593,14 @@ void bdi_update_bandwidth(struct backing
if (elapsed <= HZ / 5)
goto unlock;
+ if (thresh &&
+ now - default_backing_dev_info.bw_time_stamp >= HZ / 5) {
+ bdi_update_dirty_smooth(&default_backing_dev_info, dirty);
+ default_backing_dev_info.bw_time_stamp = now;
+ }
+ if (thresh) {
+ bdi_update_dirty_smooth(bdi, bdi_dirty);
+ }
__bdi_update_write_bandwidth(bdi, elapsed, written);
snapshot:
--- linux-next.orig/include/linux/backing-dev.h 2011-04-13 17:18:12.000000000 +0800
+++ linux-next/include/linux/backing-dev.h 2011-04-13 17:18:12.000000000 +0800
@@ -77,6 +77,8 @@ struct backing_dev_info {
unsigned long written_stamp;
unsigned long write_bandwidth;
unsigned long avg_write_bandwidth;
+ unsigned long avg_dirty;
+ unsigned long old_dirty;
struct prop_local_percpu completions;
int dirty_exceeded;
--- linux-next.orig/mm/backing-dev.c 2011-04-13 17:18:12.000000000 +0800
+++ linux-next/mm/backing-dev.c 2011-04-13 17:18:12.000000000 +0800
@@ -669,6 +669,9 @@ int bdi_init(struct backing_dev_info *bd
bdi->write_bandwidth = INIT_BW;
bdi->avg_write_bandwidth = INIT_BW;
+ bdi->avg_dirty = 0;
+ bdi->old_dirty = 0;
+
err = prop_local_init_percpu(&bdi->completions);
if (err) {
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Wu Fengguang <fengguang.wu@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jan Kara <jack@suse.cz>, larry <lantianyu1986@gmail.com>,
Wu Fengguang <fengguang.wu@intel.com>,
Christoph Hellwig <hch@lst.de>,
Trond Myklebust <Trond.Myklebust@netapp.com>,
Dave Chinner <david@fromorbit.com>, Theodore Ts'o <tytso@mit.edu>,
Chris Mason <chris.mason@oracle.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Mel Gorman <mel@csn.ul.ie>, Rik van Riel <riel@redhat.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Greg Thelen <gthelen@google.com>,
Minchan Kim <minchan.kim@gmail.com>,
Vivek Goyal <vgoyal@redhat.com>,
Andrea Righi <arighi@develer.com>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
linux-mm <linux-mm@kvack.org>,
linux-fsdevel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 04/12] writeback: smoothed global/bdi dirty pages
Date: Sat, 16 Apr 2011 21:25:50 +0800 [thread overview]
Message-ID: <20110416134332.918936130@intel.com> (raw)
In-Reply-To: 20110416132546.765212221@intel.com
[-- Attachment #1: writeback-smooth-dirty.patch --]
[-- Type: text/plain, Size: 4340 bytes --]
Maintain a smoothed version of dirty pages for use in the throttle
bandwidth calculations.
default_backing_dev_info.avg_dirty holds the smoothed global dirty
pages.
The calculation favors smoothness rather than accuracy. It's non-sense
trying to track a much fluctuated value "accurately". And its users
don't really rely on it being accurate.
CC: larry <lantianyu1986@gmail.com>
Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
---
include/linux/backing-dev.h | 2 +
mm/backing-dev.c | 3 +
mm/page-writeback.c | 66 ++++++++++++++++++++++++++++++++++
3 files changed, 71 insertions(+)
--- linux-next.orig/mm/page-writeback.c 2011-04-13 17:18:12.000000000 +0800
+++ linux-next/mm/page-writeback.c 2011-04-13 17:18:12.000000000 +0800
@@ -471,6 +471,64 @@ unsigned long bdi_dirty_limit(struct bac
return bdi_dirty;
}
+static void bdi_update_dirty_smooth(struct backing_dev_info *bdi,
+ unsigned long dirty)
+{
+ unsigned long avg = bdi->avg_dirty;
+ unsigned long old = bdi->old_dirty;
+
+ if (unlikely(!avg)) {
+ avg = dirty;
+ goto update;
+ }
+
+ /*
+ * dirty pages are departing upwards, follow up
+ */
+ if (avg < old && old <= dirty) {
+ avg += (old - avg) >> 2;
+ goto update;
+ }
+
+ /*
+ * dirty pages are departing downwards, follow down
+ */
+ if (avg > old && old >= dirty) {
+ avg -= (avg - old) >> 2;
+ goto update;
+ }
+
+ /*
+ * This can filter out one half unnecessary updates when bdi_dirty is
+ * fluctuating around the balance point, and is most effective on XFS,
+ * whose pattern is
+ * .
+ * [.] dirty [-] avg . .
+ * . .
+ * . . . . . .
+ * --------------------------------------- . .
+ * . . . . . .
+ * . . . . . .
+ * . . . . . .
+ * . . . . . .
+ * . . . .
+ * . . . . (fluctuated)
+ * . . . .
+ * . . . .
+ *
+ * @avg will remain flat at the cost of being biased towards high. In
+ * practice the error tend to be much smaller: thanks to more coarse
+ * grained fluctuations, @avg becomes the real average number for the
+ * last two rising lines of @dirty.
+ */
+ goto out;
+
+update:
+ bdi->avg_dirty = avg;
+out:
+ bdi->old_dirty = dirty;
+}
+
static void __bdi_update_write_bandwidth(struct backing_dev_info *bdi,
unsigned long elapsed,
unsigned long written)
@@ -535,6 +593,14 @@ void bdi_update_bandwidth(struct backing
if (elapsed <= HZ / 5)
goto unlock;
+ if (thresh &&
+ now - default_backing_dev_info.bw_time_stamp >= HZ / 5) {
+ bdi_update_dirty_smooth(&default_backing_dev_info, dirty);
+ default_backing_dev_info.bw_time_stamp = now;
+ }
+ if (thresh) {
+ bdi_update_dirty_smooth(bdi, bdi_dirty);
+ }
__bdi_update_write_bandwidth(bdi, elapsed, written);
snapshot:
--- linux-next.orig/include/linux/backing-dev.h 2011-04-13 17:18:12.000000000 +0800
+++ linux-next/include/linux/backing-dev.h 2011-04-13 17:18:12.000000000 +0800
@@ -77,6 +77,8 @@ struct backing_dev_info {
unsigned long written_stamp;
unsigned long write_bandwidth;
unsigned long avg_write_bandwidth;
+ unsigned long avg_dirty;
+ unsigned long old_dirty;
struct prop_local_percpu completions;
int dirty_exceeded;
--- linux-next.orig/mm/backing-dev.c 2011-04-13 17:18:12.000000000 +0800
+++ linux-next/mm/backing-dev.c 2011-04-13 17:18:12.000000000 +0800
@@ -669,6 +669,9 @@ int bdi_init(struct backing_dev_info *bd
bdi->write_bandwidth = INIT_BW;
bdi->avg_write_bandwidth = INIT_BW;
+ bdi->avg_dirty = 0;
+ bdi->old_dirty = 0;
+
err = prop_local_init_percpu(&bdi->completions);
if (err) {
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-04-16 14:06 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-16 13:25 [PATCH 00/12] IO-less dirty throttling v7 Wu Fengguang
2011-04-16 13:25 ` Wu Fengguang
2011-04-16 13:25 ` Wu Fengguang
2011-04-16 13:25 ` [PATCH 01/12] writeback: account per-bdi accumulated written pages Wu Fengguang
2011-04-16 13:25 ` Wu Fengguang
2011-04-16 13:25 ` Wu Fengguang
2011-04-16 13:25 ` [PATCH 02/12] writeback: account per-bdi accumulated dirtied pages Wu Fengguang
2011-04-16 13:25 ` Wu Fengguang
2011-04-16 13:25 ` [PATCH 03/12] writeback: bdi write bandwidth estimation Wu Fengguang
2011-04-16 13:25 ` Wu Fengguang
2011-04-16 13:25 ` Wu Fengguang
2011-04-16 13:25 ` Wu Fengguang [this message]
2011-04-16 13:25 ` [PATCH 04/12] writeback: smoothed global/bdi dirty pages Wu Fengguang
2011-04-16 13:25 ` Wu Fengguang
2011-04-16 13:25 ` [PATCH 05/12] writeback: smoothed dirty threshold and limit Wu Fengguang
2011-04-16 13:25 ` Wu Fengguang
2011-04-16 13:25 ` Wu Fengguang
2011-04-16 13:25 ` [PATCH 06/12] writeback: enforce 1/4 gap between the dirty/background thresholds Wu Fengguang
2011-04-16 13:25 ` Wu Fengguang
2011-04-16 13:25 ` [PATCH 07/12] writeback: base throttle bandwidth and position ratio Wu Fengguang
2011-04-16 13:25 ` Wu Fengguang
2011-04-16 13:25 ` Wu Fengguang
2011-04-16 13:25 ` [PATCH 08/12] writeback: IO-less balance_dirty_pages() Wu Fengguang
2011-04-16 13:25 ` Wu Fengguang
2011-04-16 13:25 ` [PATCH 09/12] writeback: show bdi write bandwidth in debugfs Wu Fengguang
2011-04-16 13:25 ` Wu Fengguang
2011-04-16 13:25 ` Wu Fengguang
2011-04-16 13:25 ` [PATCH 10/12] writeback: trace dirty_ratelimit Wu Fengguang
2011-04-16 13:25 ` Wu Fengguang
2011-04-16 13:25 ` [PATCH 11/12] writeback: trace balance_dirty_pages Wu Fengguang
2011-04-16 13:25 ` Wu Fengguang
2011-04-16 13:25 ` [PATCH 12/12] writeback: trace global_dirty_state Wu Fengguang
2011-04-16 13:25 ` Wu Fengguang
2011-04-16 16:27 ` [PATCH 00/12] IO-less dirty throttling v7 Sedat Dilek
2011-04-17 1:44 ` Wu Fengguang
2011-04-17 3:18 ` Sedat Dilek
2011-04-17 4:10 ` Wu Fengguang
2011-04-17 4:10 ` Wu Fengguang
2011-04-17 4:10 ` Wu Fengguang
2011-04-17 4:46 ` Sedat Dilek
2011-04-17 4:46 ` Sedat Dilek
2011-04-17 6:46 ` Sedat Dilek
2011-04-18 0:13 ` Wu Fengguang
2011-04-18 0:13 ` Wu Fengguang
2011-04-18 6:57 ` Sedat Dilek
2011-04-18 8:18 ` Wu Fengguang
2011-04-18 10:22 ` Sedat Dilek
2011-04-17 7:31 ` Marco Stornelli
2011-04-17 7:31 ` Marco Stornelli
2011-04-17 9:30 ` Wu Fengguang
2011-04-17 9:30 ` Wu Fengguang
2011-04-17 17:44 ` Marco Stornelli
2011-04-17 17:44 ` Marco Stornelli
2011-04-17 23:31 ` Wu Fengguang
2011-04-17 23:31 ` Wu Fengguang
2011-04-26 17:19 ` Vivek Goyal
2011-04-26 17:19 ` Vivek Goyal
2011-04-28 14:27 ` Wu Fengguang
2011-04-28 14:27 ` Wu Fengguang
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=20110416134332.918936130@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=lantianyu1986@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.