Re: [patch] mm, page_alloc: wakeup kcompactd even if kswapd cannot free more memory

[David Rientjes]

On Tue, 20 Mar 2018, Vlastimil Babka wrote:

> > Kswapd will not wakeup if per-zone watermarks are not failing or if too
> > many previous attempts at background reclaim have failed.
> > 
> > This can be true if there is a lot of free memory available.  For high-
> > order allocations, kswapd is responsible for waking up kcompactd for
> > background compaction.  If the zone is now below its watermarks or
>                                          not ?
> 

Good catch, Andrew please let me know if you would like a resend to 
correct this.