From: Pratyush Yadav <pratyush@kernel.org>
To: Tarun Sahu <tarunsahu@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
dmatlack@google.com, Mike Rapoport <rppt@kernel.org>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
dev.jain@arm.com, Pratyush Yadav <pratyush@kernel.org>,
linux-mm@kvack.org
Subject: Re: [PATCH v2 1/2] memblock: drop for_each_memblock_type() and open code its users
Date: Fri, 18 Sep 2026 02:38:04 +0200 [thread overview]
Message-ID: <2vxzwlsj5r83.fsf@kernel.org> (raw)
In-Reply-To: <20260918002239.4024231-1-tarunsahu@google.com> (Tarun Sahu's message of "Fri, 18 Sep 2026 00:22:38 +0000")
On Fri, Sep 18 2026, Tarun Sahu wrote:
> for_each_memblock_type() always starts the iteration at index 0 and its
> body is a trivial 'for' loop, so it hides very little. It also gets in
> the way of iterating from an arbitrary index, which the next patch
> needs.
>
> Remove the macro and open code its three users: memblock_add_range(),
> memblock_isolate_range() and memblock_dump(). While at it, move the
> region pointer into the loop body scope.
>
> No functional change.
>
> Signed-off-by: Tarun Sahu <tarunsahu@google.com>
> ---
> mm/memblock.c | 14 ++++++--------
> 1 file changed, 6 insertions(+), 8 deletions(-)
>
> diff --git a/mm/memblock.c b/mm/memblock.c
> index 9ce86349a29f..5aae75d34dec 100644
> --- a/mm/memblock.c
> +++ b/mm/memblock.c
> @@ -155,11 +155,6 @@ struct memblock_type physmem = {
> */
> static __refdata struct memblock_type *memblock_memory = &memblock.memory;
>
> -#define for_each_memblock_type(i, memblock_type, rgn) \
> - for (i = 0, rgn = &memblock_type->regions[0]; \
> - i < memblock_type->cnt; \
> - i++, rgn = &memblock_type->regions[i])
> -
> #define memblock_dbg(fmt, ...) \
> do { \
> if (memblock_debug) \
> @@ -651,7 +646,8 @@ static int __init_memblock memblock_add_range(struct memblock_type *type,
> base = obase;
> nr_new = 0;
>
> - for_each_memblock_type(idx, type, rgn) {
> + for (idx = 0; idx < type->cnt; idx++) {
> + rgn = &type->regions[idx];
Nit: this is really odd to read. You assign rgn and then declare rbase
and rend. Doesn't checkpatch complain?
Regardless, I reckon it would be a lot nicer to read of you move the
declaration of rgn into the loop. Same for the others below.
LGTM otherwise, so after fixing this up, feel free to add:
Reviewed-by: Pratyush Yadav <pratyush@kernel.org>
> phys_addr_t rbase = rgn->base;
> phys_addr_t rend = rbase + rgn->size;
>
> @@ -827,7 +823,8 @@ static int __init_memblock memblock_isolate_range(struct memblock_type *type,
> if (memblock_double_array(type, base, size) < 0)
> return -ENOMEM;
>
> - for_each_memblock_type(idx, type, rgn) {
> + for (idx = 0; idx < type->cnt; idx++) {
> + rgn = &type->regions[idx];
> phys_addr_t rbase = rgn->base;
> phys_addr_t rend = rbase + rgn->size;
>
> @@ -2198,7 +2195,8 @@ static void __init_memblock memblock_dump(struct memblock_type *type)
>
> pr_info(" %s.cnt = 0x%lx\n", type->name, type->cnt);
>
> - for_each_memblock_type(idx, type, rgn) {
> + for (idx = 0; idx < type->cnt; idx++) {
> + rgn = &type->regions[idx];
> char nid_buf[32] = "";
>
> base = rgn->base;
--
Regards,
Pratyush Yadav
prev parent reply other threads:[~2026-09-18 0:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 0:22 Tarun Sahu
2026-09-18 0:22 ` [PATCH v2 2/2] memblock: use binary search to locate candidate regions Tarun Sahu
2026-09-18 0:28 ` sashiko-bot
2026-09-18 0:28 ` [PATCH v2 1/2] memblock: drop for_each_memblock_type() and open code its users sashiko-bot
2026-09-18 0:38 ` Pratyush Yadav [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2vxzwlsj5r83.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dev.jain@arm.com \
--cc=dmatlack@google.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=rppt@kernel.org \
--cc=tarunsahu@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®