diff options
| author | Jianyu Zhan <nasa4836@gmail.com> | 2014-06-04 16:10:58 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2014-06-04 16:54:13 -0700 |
| commit | d2f3102838d90ed6ed09a6154bdb2306f7cf1548 (patch) | |
| tree | e6b1f767b51051e0c5b68994f5c1fd3ef5e4f877 /mm | |
| parent | 50088c440910730baf3248acfad2c846fb3eea77 (diff) | |
| download | kernel-common-d2f3102838d90ed6ed09a6154bdb2306f7cf1548.tar.gz kernel-common-d2f3102838d90ed6ed09a6154bdb2306f7cf1548.tar.bz2 kernel-common-d2f3102838d90ed6ed09a6154bdb2306f7cf1548.zip | |
mm/page-writeback.c: remove outdated comment
There is an orphaned prehistoric comment , which used to be against
get_dirty_limits(), the dawn of global_dirtyable_memory().
Back then, the implementation of get_dirty_limits() is complicated and
full of magic numbers, so this comment is necessary. But we now use the
clear and neat global_dirtyable_memory(), which renders this comment
ambiguous and useless. Remove it.
Signed-off-by: Jianyu Zhan <nasa4836@gmail.com>
Acked-by: Johannes Weiner <hannes@cmpxchg.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm')
| -rw-r--r-- | mm/page-writeback.c | 18 |
1 files changed, 0 insertions, 18 deletions
diff --git a/mm/page-writeback.c b/mm/page-writeback.c index b9b8e8204628..533fa60c9ac1 100644 --- a/mm/page-writeback.c +++ b/mm/page-writeback.c @@ -156,24 +156,6 @@ static unsigned long writeout_period_time = 0; #define VM_COMPLETIONS_PERIOD_LEN (3*HZ) /* - * Work out the current dirty-memory clamping and background writeout - * thresholds. - * - * The main aim here is to lower them aggressively if there is a lot of mapped - * memory around. To avoid stressing page reclaim with lots of unreclaimable - * pages. It is better to clamp down on writers than to start swapping, and - * performing lots of scanning. - * - * We only allow 1/2 of the currently-unmapped memory to be dirtied. - * - * We don't permit the clamping level to fall below 5% - that is getting rather - * excessive. - * - * We make sure that the background writeout level is below the adjusted - * clamping level. - */ - -/* * In a memory zone, there is a certain amount of pages we consider * available for the page cache, which is essentially the number of * free and reclaimable pages, minus some zone reserves to protect |