[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <218b81f2-3ed4-4389-b08b-c26dd8c0a4bc@suse.cz>
Date: Tue, 25 Feb 2025 12:05:16 +0100
From: Vlastimil Babka <vbabka@...e.cz>
To: Brendan Jackman <jackmanb@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>
Cc: Mel Gorman <mgorman@...hsingularity.net>, Michal Hocko
<mhocko@...nel.org>, Johannes Weiner <hannes@...xchg.org>,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Yosry Ahmed <yosry.ahmed@...ux.dev>
Subject: Re: [PATCH v2 1/2] mm/page_alloc: Clarify terminology in migratetype
fallback code
On 2/24/25 19:42, Brendan Jackman wrote:
> On Mon, 24 Feb 2025 at 13:37, Brendan Jackman <jackmanb@...gle.com> wrote:
>> int find_suitable_fallback(struct free_area *area, unsigned int order,
>> - int migratetype, bool only_stealable, bool *can_steal);
>> + int migratetype, bool need_whole_block, bool *whole_block);
>
> Agh, sorry, I was meant to rename all of these to claim_block.
> Apparently I got halfway through doing that then got distracted.
>
> (Literally the whole point of this patch was to clean this up, and I
> somehow failed to actually do that!)
Given Johannes' patches went to mm-unstable meanwhile, this now expectedly
conflicts a lot so I'll wait with review for a new rebased version. Thanks!
Powered by blists - more mailing lists