From: Oscar Salvador <osalvador@suse.de>
To: David Hildenbrand <david@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@kernel.org>,
Wei Yang <richard.weiyang@gmail.com>,
Miaohe Lin <linmiaohe@huawei.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] mm/page_alloc: Do not calculate node's total pages and memmap pages when empty
Date: Thu, 5 May 2022 11:09:18 +0200 [thread overview]
Message-ID: <YnOUPoqM3RncmraS@localhost.localdomain> (raw)
In-Reply-To: <f31caf6a-fb13-0be3-9fa2-0b4959cc0810@redhat.com>
On Thu, Apr 28, 2022 at 02:13:46PM +0200, David Hildenbrand wrote:
> Sorry, I'm late with review. My mailbox got flooded.
Hi David :)
> > + /* Skip calculation for memoryless nodes */
> > + if (node_start_pfn == node_end_pfn)
> > + goto no_pages;
> > +
>
> Just a NIT:
>
> E.g., in zone_spanned_pages_in_node() we test for
> !node_start_pfn && !node_end_pfn
>
> In update_pgdat_span(), we set
> node_start_pfn = node_end_pfn = 0;
> when we find an empty node during memory unplug.
>
> Therefore, I wonder if a helper "is_memoryless_node()" or "node_empty()"
> might be reasonable, that just checks for either
> !node_start_pfn && !node_end_pfn
> or
> node_start_pfn == node_end_pfn
Yeah, I thoguth about that as well, but given the few places we check
for it I was hesitant to add it.
But it might make the situation more clear, so I will go with a helper.
> > +no_pages:
> > zone_init_internals(zone, j, nid, freesize);
> >
> > if (!size)
>
> We have another size check below. We essentially have right now:
>
> "
> if (!size)
> goto no_pages;
>
> [code]
> no_pages:
> zone_init_internals(zone, j, nid, freesize);
>
> if (!size)
> continue
> [more code]
> "
>
> IMHO, it would be nicer to avoid the label/goto by just doing a:
>
> "
> if (!size) {
> zone_init_internals(zone, j, nid, 0);
> continue;
> }
>
> [code]
> zone_init_internals(zone, j, nid, freesize);
> [more code]
> "
>
> Or factoring out [code] into a separate function.
I did not think about how a refactor would look, so for now I will go
with your first proposal. If I see that a refactor is due, I will think
more about it.
thanks!
--
Oscar Salvador
SUSE Labs
next prev parent reply other threads:[~2022-05-05 9:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 15:07 [PATCH 0/3] A minor hotplug refactoring Oscar Salvador
2022-03-07 15:07 ` [PATCH 1/3] mm/page_alloc: Do not calculate node's total pages and memmap pages when empty Oscar Salvador
2022-04-28 12:13 ` David Hildenbrand
2022-05-05 9:09 ` Oscar Salvador [this message]
2022-03-07 15:07 ` [PATCH 2/3] mm/memory_hotplug: Reset node's state when empty during offline Oscar Salvador
2022-04-28 12:30 ` David Hildenbrand
2022-05-05 10:37 ` Oscar Salvador
2022-03-07 15:07 ` [PATCH 3/3] mm/memory_hotplug: Refactor hotadd_init_pgdat and try_online_node Oscar Salvador
2022-04-28 12:35 ` David Hildenbrand
2022-05-05 9:17 ` Oscar Salvador
2022-04-27 21:05 ` [PATCH 0/3] A minor hotplug refactoring Andrew Morton
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=YnOUPoqM3RncmraS@localhost.localdomain \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=richard.weiyang@gmail.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;
as well as URLs for NNTP newsgroup(s).