A-Team_Digital_Solutions/android_kernel_motorola_sm6375
Watch
2
0
Fork
You've already forked android_kernel_motorola_sm6375
 0
mirror of https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git synced 2026-10-28 02:32:09 -04:00
Code Issues Projects Releases Packages Wiki Activity

remove PAGE_GROUP_BY_MOBILITY

Browse source 
Grouping pages by mobility can be disabled at compile-time. This was
considered undesirable by a number of people. However, in the current stack of
patches, it is not a simple case of just dropping the configurable patch as it
would cause merge conflicts.  This patch backs out the configuration option.

Signed-off-by: Mel Gorman <[email protected]>
Acked-by: Andy Whitcroft <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
This commit is contained in:
Mel Gorman 2007-10-16 01:25:58 -07:00 • committed by Linus Torvalds
commit ac0e5b7a6b
3 changed files with 2 additions and 62 deletions
Download patch file Download diff file Expand all files Collapse all files

13
init/Kconfig
View file

@ -607,19 +607,6 @@ config BASE_SMALL
default 0 if BASE_FULL
default 1 if !BASE_FULL
config PAGE_GROUP_BY_MOBILITY
bool "Group pages based on their mobility in the page allocator"
def_bool y
help
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
menuconfig MODULES
bool "Enable loadable module support"
help