|author||Mel Gorman <firstname.lastname@example.org>||2007-10-16 01:25:50 -0700|
|committer||Linus Torvalds <email@example.com>||2007-10-16 09:42:59 -0700|
Add a configure option to group pages by mobility
The grouping mechanism has some memory overhead and a more complex allocation path. This patch allows the strategy to be disabled for small memory systems or if it is known the workload is suffering because of the strategy. It also acts to show where the page groupings strategy interacts with the standard buddy allocator. Signed-off-by: Mel Gorman <firstname.lastname@example.org> Signed-off-by: Joel Schopp <email@example.com> Cc: Andy Whitcroft <firstname.lastname@example.org> Signed-off-by: Andrew Morton <email@example.com> Signed-off-by: Linus Torvalds <firstname.lastname@example.org>
Diffstat (limited to 'init')
1 files changed, 13 insertions, 0 deletions
diff --git a/init/Kconfig b/init/Kconfig
index 54f31a191b8..bab643f7717 100644
@@ -607,6 +607,19 @@ config BASE_SMALL
default 0 if BASE_FULL
default 1 if !BASE_FULL
+ bool "Group pages based on their mobility in the page allocator"
+ def_bool y
+ The standard allocator will fragment memory over time which means
+ that high order allocations will fail even if kswapd is running. If
+ this option is set, the allocator will try and group page types
+ based on their ability to migrate or reclaim. This is a best effort
+ attempt at lowering fragmentation which a few workloads care about.
+ The loss is a more complex allocator that may perform slower. If
+ you are interested in working with large pages, say Y and set
+ /proc/sys/vm/min_free_bytes to 16374. Otherwise say N
bool "Enable loadable module support"