[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+i-1C0J5DiFXB3begMqe+TeuFDHqaGc1cg5C9z3=_ue6q0KLg@mail.gmail.com>
Date: Mon, 24 Feb 2025 19:42:21 +0100
From: Brendan Jackman <jackmanb@...gle.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Vlastimil Babka <vbabka@...e.cz>, 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 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!)
Powered by blists - more mailing lists