[ckpatch][26/29] mm-set_zero_dirty_ratio.patch

[Con Kolivas]

Set dirty_ratio to 0 by default. This makes processes doing file writes more
responsible for any I/O induced delays by throttling them very early instead
of handing off the workload to a pdflush thread. This improves latencies for
small writes and any reads in the presence of heavy writes. It also helps
preserve more mapped pages and useful pagecache by not ever having large
amounts of dirty data taking up ram.

Signed-off-by: Con Kolivas <kernel@xxxxxxxxxxx>

---
 mm/page-writeback.c |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)

Index: linux-ck-dev/mm/page-writeback.c
===================================================================
--- linux-ck-dev.orig/mm/page-writeback.c	2006-06-18 15:25:16.000000000 +1000
+++ linux-ck-dev/mm/page-writeback.c	2006-06-18 15:25:22.000000000 +1000
@@ -64,33 +64,33 @@ static inline long sync_writeback_pages(
 /*
  * Start background writeback (via pdflush) at this percentage
  */
-int dirty_background_ratio = 10;
+int dirty_background_ratio __read_mostly = 10;
 
 /*
  * The generator of dirty data starts writeback at this percentage
  */
-int vm_dirty_ratio = 40;
+int vm_dirty_ratio __read_mostly;
 
 /*
  * The interval between `kupdate'-style writebacks, in jiffies
  */
-int dirty_writeback_interval = 5 * HZ;
+int dirty_writeback_interval __read_mostly = 5 * HZ;
 
 /*
  * The longest number of jiffies for which data is allowed to remain dirty
  */
-int dirty_expire_interval = 30 * HZ;
+int dirty_expire_interval __read_mostly = 30 * HZ;
 
 /*
  * Flag that makes the machine dump writes/reads and block dirtyings.
  */
-int block_dump;
+int block_dump __read_mostly;
 
 /*
  * Flag that puts the machine in "laptop mode". Doubles as a timeout in jiffies:
  * a full sync is triggered after this time elapses without any disk activity.
  */
-int laptop_mode;
+int laptop_mode __read_mostly;
 
 EXPORT_SYMBOL(laptop_mode);
 

-- 
-ck
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/