[PATCH 0/2] Reduce number of GFP_ATOMIC allocation failures · Mel Gorman <hidden> · 2009-10-16
[PATCH 2/2] page allocator: Direct reclaim should always obey watermarks · Mel Gorman <hidden> · 2009-10-16
Re: [PATCH 2/2] page allocator: Direct reclaim should always obey watermarks · David Rientjes <rientjes@google.com> · 2009-10-16
Re: [PATCH 2/2] page allocator: Direct reclaim should always obey watermarks · Mel Gorman <hidden> · 2009-10-16
Re: [PATCH 2/2] page allocator: Direct reclaim should always obey watermarks · Frans Pop <hidden> · 2009-10-16
Re: [PATCH 2/2] page allocator: Direct reclaim should always obey watermarks · Frans Pop <hidden> · 2009-10-27
[PATCH 1/2] page allocator: Always wake kswapd when restarting an allocation attempt after direct reclaim failed · Mel Gorman <hidden> · 2009-10-16
Re: [PATCH 1/2] page allocator: Always wake kswapd when restarting an allocation attempt after direct reclaim failed · Pekka Enberg <hidden> · 2009-10-16
Re: [PATCH 1/2] page allocator: Always wake kswapd when restarting an allocation attempt after direct reclaim failed · Christoph Lameter <hidden> · 2009-10-19
Re: [PATCH 0/2] Reduce number of GFP_ATOMIC allocation failures · Karol Lewandowski <hidden> · 2009-10-17
Re: [PATCH 0/2] Reduce number of GFP_ATOMIC allocation failures · Karol Lewandowski <hidden> · 2009-10-18
Re: [PATCH 0/2] Reduce number of GFP_ATOMIC allocation failures · Frans Pop <hidden> · 2009-10-18
Re: [PATCH 0/2] Reduce number of GFP_ATOMIC allocation failures · Karol Lewandowski <hidden> · 2009-10-19
Re: [PATCH 0/2] Reduce number of GFP_ATOMIC allocation failures · Mel Gorman <hidden> · 2009-10-19

Re: [PATCH 1/2] page allocator: Always wake kswapd when restarting an allocation attempt after direct reclaim failed

From: Christoph Lameter <hidden>
Date: 2009-10-19 08:06:17
Also in: linux-mm, lkml


Reviewed-by: Christoph Lameter <redacted>

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help