| commit | c8462cc9de9e92264ec647903772f6036a99b286 | |
| author | Wu Fengguang <fengguang.wu@intel.com> | |
| Sun, 12 Jun 2011 01:21:43 +0000 (11 19:21 -0600) | ||
| committer | Wu Fengguang <fengguang.wu@intel.com> | |
| Mon, 3 Oct 2011 13:08:57 +0000 (3 21:08 +0800) | ||
| tree | f442132f53651a04e67f3a119ead9f54be51a6cb | treesnapshot (tar.gz zip) |
| parent | 143dfe8611a63030ce0c79419dc362f7838be557 | commitdiff |
writeback: limit max dirty pause time
Apply two policies to scale down the max pause time for
1) small number of concurrent dirtiers
2) small memory system (comparing to storage bandwidth)
MAX_PAUSE=200ms may only be suitable for high end servers with lots of
concurrent dirtiers, where the large pause time can reduce much overheads.
Otherwise, smaller pause time is desirable whenever possible, so as to
get good responsiveness and smooth user experiences. It's actually
required for good disk utilization in the case when all the dirty pages
can be synced to disk within MAX_PAUSE=200ms.
Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
Apply two policies to scale down the max pause time for
1) small number of concurrent dirtiers
2) small memory system (comparing to storage bandwidth)
MAX_PAUSE=200ms may only be suitable for high end servers with lots of
concurrent dirtiers, where the large pause time can reduce much overheads.
Otherwise, smaller pause time is desirable whenever possible, so as to
get good responsiveness and smooth user experiences. It's actually
required for good disk utilization in the case when all the dirty pages
can be synced to disk within MAX_PAUSE=200ms.
Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
| mm/page-writeback.c | diffblobblamehistory |