diff options
author | Johannes Weiner <hannes@cmpxchg.org> | 2013-12-20 14:54:12 (GMT) |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-01-09 20:25:14 (GMT) |
commit | f9f4487e62cd8659c85b3f9a69bfb5925f362672 (patch) | |
tree | 02980905cb7b9b42f7577594b3c0f4c8b1fa2b19 /arch/m32r/kernel/traps.c | |
parent | 99355d51e3267ad7da0f48d4aaa8f354b47d85eb (diff) | |
download | linux-fsl-qoriq-f9f4487e62cd8659c85b3f9a69bfb5925f362672.tar.xz |
mm: page_alloc: revert NUMA aspect of fair allocation policy
commit fff4068cba484e6b0abe334ed6b15d5a215a3b25 upstream.
Commit 81c0a2bb515f ("mm: page_alloc: fair zone allocator policy") meant
to bring aging fairness among zones in system, but it was overzealous
and badly regressed basic workloads on NUMA systems.
Due to the way kswapd and page allocator interacts, we still want to
make sure that all zones in any given node are used equally for all
allocations to maximize memory utilization and prevent thrashing on the
highest zone in the node.
While the same principle applies to NUMA nodes - memory utilization is
obviously improved by spreading allocations throughout all nodes -
remote references can be costly and so many workloads prefer locality
over memory utilization. The original change assumed that
zone_reclaim_mode would be a good enough predictor for that, but it
turned out to be as indicative as a coin flip.
Revert the NUMA aspect of the fairness until we can find a proper way to
make it configurable and agree on a sane default.
Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
Reviewed-by: Michal Hocko <mhocko@suse.cz>
Signed-off-by: Mel Gorman <mgorman@suse.de>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch/m32r/kernel/traps.c')
0 files changed, 0 insertions, 0 deletions