linux-kernel - Re: [PATCH 2/2] mm/page_alloc: fix never set ALLOC

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20190424154624.f1084195c36684453a557718@linux-foundation.org>
Date:   Wed, 24 Apr 2019 15:46:24 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Mel Gorman <mgorman@...hsingularity.net>
Cc:     Andrey Ryabinin <aryabinin@...tuozzo.com>, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] mm/page_alloc: fix never set ALLOC_NOFRAGMENT flag

On Wed, 24 Apr 2019 10:04:03 +0100 Mel Gorman <mgorman@...hsingularity.net> wrote:

> On Tue, Apr 23, 2019 at 12:01:43PM -0700, Andrew Morton wrote:
> > On Tue, 23 Apr 2019 15:08:06 +0300 Andrey Ryabinin <aryabinin@...tuozzo.com> wrote:
> > 
> > > Commit 0a79cdad5eb2 ("mm: use alloc_flags to record if kswapd can wake")
> > > removed setting of the ALLOC_NOFRAGMENT flag. Bring it back.
> > 
> > What are the runtime effects of this fix?
> 
> The runtime effect is that ALLOC_NOFRAGMENT behaviour is restored so
> that allocations are spread across local zones to avoid fragmentation
> due to mixing pageblocks as long as possible.

OK, thanks.  Is this worth a -stable backport?