[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6f2708406372450edb39ed6ed5a5d0bc112c84af.camel@surriel.com>
Date: Tue, 16 Sep 2025 18:57:44 -0400
From: Rik van Riel <riel@...riel.com>
To: Frank van der Linden <fvdl@...gle.com>, akpm@...ux-foundation.org,
muchun.song@...ux.dev, linux-mm@...ck.org, linux-kernel@...r.kernel.org
Cc: hannes@...xchg.org, david@...hat.com, roman.gushchin@...ux.dev
Subject: Re: [RFC PATCH 05/12] mm/cma: add helper functions for CMA balancing
On Mon, 2025-09-15 at 19:51 +0000, Frank van der Linden wrote:
>
> +/*
> + * Provide the next free range in a cma memory range, as derived
> + * from the bitmap.
> + *
> + * @cmr: memory range to scan
> + * @start_pfn: the beginning of the previous range
> + * @end_pfn: the end of the previous range, zero for the first call
> + *
> + * The caller can adjust *end_pfn end use it as a starting point.
> + */
The function documentation does not really make it clear
that start_pfn and end_pfn are also used for the function
OUTPUT, and that the return value indicates whether or
not a next area was found.
Same for cma_next_noncma_pagerange. Other than that, this
looks reasonable so far.
--
All Rights Reversed.
Powered by blists - more mailing lists