The patch titled readahead: kconfig option READAHEAD_SMOOTH_AGING has been added to the -mm tree. Its filename is readahead-state-based-method-aging-accounting-readahead-kconfig-option-readahead_smooth_aging.patch See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find out what to do about this ------------------------------------------------------ Subject: readahead: kconfig option READAHEAD_SMOOTH_AGING From: Wu Fengguang <wfg@xxxxxxxxxxxxxxxx> Make the kconfig option READAHEAD_SMOOTH_AGING depend on READAHEAD_ALLOW_OVERHEADS, and turned off by default. Signed-off-by: Wu Fengguang <wfg@xxxxxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxx> --- mm/Kconfig | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff -puN mm/Kconfig~readahead-state-based-method-aging-accounting-readahead-kconfig-option-readahead_smooth_aging mm/Kconfig --- a/mm/Kconfig~readahead-state-based-method-aging-accounting-readahead-kconfig-option-readahead_smooth_aging +++ a/mm/Kconfig @@ -216,6 +216,14 @@ config DEBUG_READAHEAD Say N for production servers. config READAHEAD_SMOOTH_AGING - def_bool n if NUMA - default y if !NUMA - depends on ADAPTIVE_READAHEAD + bool "Fine grained readahead aging" + default n + depends on READAHEAD_ALLOW_OVERHEADS && !NUMA + help + Enable fine grained, mooth accounting of readahead aging. + + It can help servers which meet the following two conditions: + - have large number of concurrent readers + - have the danger of readahead thrashing(i.e. memory tight) + + This feature is only available on non-NUMA systems. _ Patches currently in -mm which might be from wfg@xxxxxxxxxxxxxxxx are origin.patch readahead-kconfig-options.patch readahead-kconfig-option-readahead_allow_overheads.patch radixtree-introduce-radix_tree_scan_hole.patch mm-introduce-probe_page.patch mm-introduce-pg_readahead.patch readahead-add-look-ahead-support-to-__do_page_cache_readahead.patch readahead-delay-page-release-in-do_generic_mapping_read.patch readahead-insert-cond_resched-calls.patch readahead-minmax_ra_pages.patch readahead-events-accounting.patch readahead-rescue_pages.patch readahead-sysctl-parameters.patch readahead-sysctl-parameters-fix.patch readahead-min-max-sizes.patch readahead-state-based-method-aging-accounting.patch readahead-state-based-method-routines.patch readahead-state-based-method-routines-no-ra_flag_eof-on-single-page-file.patch readahead-state-based-method.patch readahead-state-based-method-readahead-state-based-method-stand-alone-size-limit-code.patch readahead-state-based-method-aging-accounting-readahead-kconfig-option-readahead_smooth_aging.patch readahead-context-based-method.patch readahead-context-based-method-apply-stream_shift-size-limits-to-contexta-method.patch readahead-context-based-method-fix-remain-counting.patch readahead-context-based-method-slow-start.patch readahead-initial-method-guiding-sizes.patch readahead-initial-method-guiding-sizes-aggressive-initial-sizes.patch readahead-initial-method-thrashing-guard-size.patch readahead-initial-method-expected-read-size.patch readahead-initial-method-user-recommended-size.patch readahead-initial-method.patch readahead-backward-prefetching-method.patch readahead-backward-prefetching-method-add-use-case-comment.patch readahead-seeking-reads-method.patch readahead-thrashing-recovery-method.patch readahead-call-scheme.patch readahead-call-scheme-fix-fastcall.patch readahead-call-scheme-no-fastcall-for-readahead_cache_hit.patch readahead-laptop-mode.patch readahead-loop-case.patch readahead-nfsd-case.patch readahead-turn-on-by-default.patch readahead-debug-radix-tree-new-functions.patch readahead-debug-traces-showing-accessed-file-names.patch readahead-debug-traces-showing-read-patterns.patch readahead-remove-size-limit-on-read_ahead_kb.patch readahead-backward-prefetching-method-fix.patch readahead-kconfig-option-readahead_hit_feedback.patch readahead-remove-the-size-limit-of-max_sectors_kb-on-read_ahead_kb.patch - To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html