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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Tue, 20 Mar 2018 13:26:16 -0700 (PDT)
From:   David Rientjes <rientjes@...gle.com>
To:     Vlastimil Babka <vbabka@...e.cz>
cc:     Andrew Morton <akpm@...ux-foundation.org>,
        Mel Gorman <mgorman@...hsingularity.net>,
        linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [patch] mm, page_alloc: wakeup kcompactd even if kswapd cannot
 free more memory

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.