path: root/mm/page_alloc.c
diff options
authorMel Gorman <>2009-11-11 14:26:14 -0800
committerLinus Torvalds <>2009-11-12 07:25:56 -0800
commitcc4a6851466039a8a688c843962a05689059ff3b (patch)
tree23e3f6c4797179d6bea91890f5784c1c0cb47aa9 /mm/page_alloc.c
parentb0c9065324b7c1242b97b27a1407da18471b9b23 (diff)
page allocator: always wake kswapd when restarting an allocation attempt after direct reclaim failed
If a direct reclaim makes no forward progress, it considers whether it should go OOM or not. Whether OOM is triggered or not, it may retry the allocation afterwards. In times past, this would always wake kswapd as well but currently, kswapd is not woken up after direct reclaim fails. For order-0 allocations, this makes little difference but if there is a heavy mix of higher-order allocations that direct reclaim is failing for, it might mean that kswapd is not rewoken for higher orders as much as it did previously. This patch wakes up kswapd when an allocation is being retried after a direct reclaim failure. It would be expected that kswapd is already awake, but this has the effect of telling kswapd to reclaim at the higher order as well. Signed-off-by: Mel Gorman <> Reviewed-by: Christoph Lameter <> Reviewed-by: Pekka Enberg <> Reviewed-by: KOSAKI Motohiro <> Cc: <> Signed-off-by: Andrew Morton <> Signed-off-by: Linus Torvalds <>
Diffstat (limited to 'mm/page_alloc.c')
1 files changed, 1 insertions, 1 deletions
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index cdcedf66161..250d0552a92 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -1817,9 +1817,9 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned int order,
goto nopage;
wake_all_kswapd(order, zonelist, high_zoneidx);
* OK, we're below the kswapd watermark and have kicked background
* reclaim. Now things get more complex, so set up alloc_flags according