[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <31b62d5d-11f6-6a68-fa04-889c98b66d9b@suse.cz>
Date: Tue, 16 Oct 2018 14:24:01 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: Andrew Morton <akpm@...ux-foundation.org>,
David Rientjes <rientjes@...gle.com>
Cc: Greg Thelen <gthelen@...gle.com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [patch] mm, page_alloc: set num_movable in move_freepages()
On 10/5/18 11:21 PM, Andrew Morton wrote:
> On Fri, 5 Oct 2018 13:56:39 -0700 (PDT) David Rientjes <rientjes@...gle.com> wrote:
>
>> If move_freepages() returns 0 because zone_spans_pfn(), *num_movable can
>
> move_free_pages_block()? !zone_spans_pfn()?
Also the subject would be more accurate if it said "initialize
num_movable in move_freepages_block()" ?
Otherwise,
Acked-by: Vlastimil Babka <vbabka@...e.cz>
>> hold the value from the stack because it does not get initialized in
>> move_freepages().
>>
>> Move the initialization to move_freepages_block() to guarantee the value
>> actually makes sense.
>>
>> This currently doesn't affect its only caller where num_movable != NULL,
>> so no bug fix, but just more robust.
>>
>> ...
>
Powered by blists - more mailing lists