summaryrefslogtreecommitdiff
path: root/include/linux/sysctl.h
diff options
context:
space:
mode:
authorAndrew Morton <akpm@digeo.com>2002-09-19 08:36:34 -0700
committerLinus Torvalds <torvalds@home.transmeta.com>2002-09-19 08:36:34 -0700
commitda1eca6061198690ea08118d78fde70216dcf093 (patch)
tree6ee637d0160948bc595dbd5ea02b7d8c5d249fe3 /include/linux/sysctl.h
parent6fda85f284986ede5458990e5b82115336d4f694 (diff)
[PATCH] remove /proc/sys/vm/dirty_sync_thresh
This was designed to be a really sterm throttling threshold: if dirty memory reaches this level then perform writeback and actually wait on it. It doesn't work. Because memory dirtiers are required to perform writeback if the amount of dirty AND writeback memory exceeds dirty_async_ratio. So kill it, and rely just on the request queues being appropriately scaled to the machine size (they are). This is basically what 2.4 does.
Diffstat (limited to 'include/linux/sysctl.h')
-rw-r--r--include/linux/sysctl.h11
1 files changed, 5 insertions, 6 deletions
diff --git a/include/linux/sysctl.h b/include/linux/sysctl.h
index 3127165e7c13..606f1385a37e 100644
--- a/include/linux/sysctl.h
+++ b/include/linux/sysctl.h
@@ -147,12 +147,11 @@ enum
VM_PAGE_CLUSTER=10, /* int: set number of pages to swap together */
VM_DIRTY_BACKGROUND=11, /* dirty_background_ratio */
VM_DIRTY_ASYNC=12, /* dirty_async_ratio */
- VM_DIRTY_SYNC=13, /* dirty_sync_ratio */
- VM_DIRTY_WB_CS=14, /* dirty_writeback_centisecs */
- VM_DIRTY_EXPIRE_CS=15, /* dirty_expire_centisecs */
- VM_NR_PDFLUSH_THREADS=16, /* nr_pdflush_threads */
- VM_OVERCOMMIT_RATIO=17, /* percent of RAM to allow overcommit in */
- VM_PAGEBUF=18 /* struct: Control pagebuf parameters */
+ VM_DIRTY_WB_CS=13, /* dirty_writeback_centisecs */
+ VM_DIRTY_EXPIRE_CS=14, /* dirty_expire_centisecs */
+ VM_NR_PDFLUSH_THREADS=15, /* nr_pdflush_threads */
+ VM_OVERCOMMIT_RATIO=16, /* percent of RAM to allow overcommit in */
+ VM_PAGEBUF=17, /* struct: Control pagebuf parameters */
};