From: tarunsahu@google.com
To: Mike Rapoport <rppt@kernel.org>
Cc: dmatlack@google.com, Pasha Tatashin <pasha.tatashin@soleen.com>,
Andrew Morton <akpm@linux-foundation.org>,
Pratyush Yadav <pratyush@kernel.org>,
kexec@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] memblock: drop for_each_memblock_type() and open code its users
Date: Tue, 13 Oct 2026 15:18:45 +0000 [thread overview]
Message-ID: <9huzecdt633e.fsf@tarunix.c.googlers.com> (raw)
In-Reply-To: <as4EcgiBH5jjww42@kernel.org>
Mike Rapoport <rppt@kernel.org> writes:
> Hi Tarun,
>
> Please for the next time add the cover-letter when sending more than one
> patch.
Thanks Mike for piking up the patches.
Sure, I will take care of adding the cover-letter.
You had some nit change suggestion, Let me know if you want
me send v5 or it is alright.
~Tarun
>
> On Thu, Oct 08, 2026 at 07:08:27PM +0000, 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.
>>
>> Reviewed-by: Pratyush Yadav <pratyush@kernel.org>
>> Signed-off-by: Tarun Sahu <tarunsahu@google.com>
>> ---
>> mm/memblock.c | 17 ++++++-----------
>> 1 file changed, 6 insertions(+), 11 deletions(-)
>>
>> diff --git a/mm/memblock.c b/mm/memblock.c
>> index f5aaa38cfa31..59dda7d085f3 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) \
>> @@ -615,7 +610,6 @@ static int __init_memblock memblock_add_range(struct memblock_type *type,
>> phys_addr_t obase = base;
>> phys_addr_t end = base + memblock_cap_size(base, &size);
>> int idx, nr_new, start_rgn = -1, end_rgn;
>> - struct memblock_region *rgn;
>>
>> if (!size)
>> return 0;
>> @@ -651,7 +645,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++) {
>> + struct memblock_region *rgn = &type->regions[idx];
>> phys_addr_t rbase = rgn->base;
>> phys_addr_t rend = rbase + rgn->size;
>>
>> @@ -815,7 +810,6 @@ static int __init_memblock memblock_isolate_range(struct memblock_type *type,
>> {
>> phys_addr_t end = base + memblock_cap_size(base, &size);
>> int idx;
>> - struct memblock_region *rgn;
>>
>> *start_rgn = *end_rgn = 0;
>>
>> @@ -827,7 +821,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++) {
>> + struct memblock_region *rgn = &type->regions[idx];
>> phys_addr_t rbase = rgn->base;
>> phys_addr_t rend = rbase + rgn->size;
>>
>> @@ -2194,11 +2189,11 @@ static void __init_memblock memblock_dump(struct memblock_type *type)
>> phys_addr_t base, end, size;
>> enum memblock_flags flags;
>> int idx;
>> - struct memblock_region *rgn;
>>
>> 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++) {
>> + struct memblock_region *rgn = &type->regions[idx];
>> char nid_buf[32] = "";
>>
>> base = rgn->base;
>> --
>> 2.56.0.385.gd3acb90ef8-goog
>>
>
> --
> Sincerely yours,
> Mike.
prev parent reply other threads:[~2026-10-13 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 19:08 [PATCH v4 1/2] memblock: drop for_each_memblock_type() and open code its users Tarun Sahu
2026-10-08 19:08 ` [PATCH v4 2/2] memblock: use binary search to locate candidate regions Tarun Sahu
2026-10-08 19:14 ` sashiko-bot
2026-10-09 17:00 ` Mike Rapoport
2026-10-08 19:12 ` [PATCH v4 1/2] memblock: drop for_each_memblock_type() and open code its users sashiko-bot
2026-10-13 10:06 ` Mike Rapoport
2026-10-13 10:14 ` Mike Rapoport
2026-10-13 15:18 ` tarunsahu [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=9huzecdt633e.fsf@tarunix.c.googlers.com \
--to=tarunsahu@google.com \
--cc=akpm@linux-foundation.org \
--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=pratyush@kernel.org \
--cc=rppt@kernel.org \
/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