> 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 > application 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 <mel@xxxxxxxxx> > Reviewed-by: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx> > Reviewed-by: Pekka Enberg <penberg@xxxxxxxxxxxxxx> > Reviewed-by: KOSAKI Motohiro <kosaki.motohiro@xxxxxxxxxxxxxx> Umm, My mail box have the carbon copy of akpm sent this patch to linus. (bellow subject and data) Does this have any update? ----------------------------------------------------------------- Subject: [patch 07/35] page allocator: always wake kswapd when restarting an allocation attempt after direct reclaim failed To: torvalds@xxxxxxxxxxxxxxxxxxxx Cc: akpm@xxxxxxxxxxxxxxxxxxxx, mel@xxxxxxxxx, cl@xxxxxxxxxxxxxxxxxxxx, kosaki.motohiro@xxxxxxxxxxxxxx, penberg@xxxxxxxxxxxxxx, stable@xxxxxxxxxx From: akpm@xxxxxxxxxxxxxxxxxxxx Date: Wed, 11 Nov 2009 14:26:14 -0800 -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
