From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Luis Chamberlain <mcgrof@kernel.org>,
akpm@linux-foundation.org, jhubbard@nvidia.com, vbabka@suse.cz,
mgorman@suse.de, linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, dave@stgolabs.net,
p.raghav@samsung.com, da.gomez@samsung.com
Subject: Re: [PATCH 2/3] mm/compaction: add and use for_each_populated_zone_pgdat() helper
Date: Thu, 14 Mar 2024 15:19:45 +0800 [thread overview]
Message-ID: <ea5d5bb6-32a5-4161-95cd-3dc916576bf7@linux.alibaba.com> (raw)
In-Reply-To: <20240314005436.2962962-3-mcgrof@kernel.org>
On 2024/3/14 08:54, Luis Chamberlain wrote:
> We can just wrap most of the work done on fragmentation_score_node()
> into a pgdat helper for populated zones. Add the helper and use it.
>
> Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
> ---
> include/linux/mmzone.h | 8 ++++++++
> mm/compaction.c | 9 ++-------
> 2 files changed, 10 insertions(+), 7 deletions(-)
>
> diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
> index a497f189d988..1fd74c7100ec 100644
> --- a/include/linux/mmzone.h
> +++ b/include/linux/mmzone.h
> @@ -1597,6 +1597,14 @@ extern struct zone *next_zone(struct zone *zone);
> ; /* do nothing */ \
> else
>
> +#define for_each_populated_zone_pgdat(zone, pgdat) \
> + for (zone = pgdat->node_zones; \
> + zone; \
> + zone = next_zone(zone)) \
> + if (!populated_zone(zone)) \
> + ; /* do nothing */ \
> + else
I think this will break the original logics, since the next_zone() will
iterate over all memory zones, instead of only the memory zones of the
specified node.
> static inline struct zone *zonelist_zone(struct zoneref *zoneref)
> {
> return zoneref->zone;
> diff --git a/mm/compaction.c b/mm/compaction.c
> index b961db601df4..023a09d0786d 100644
> --- a/mm/compaction.c
> +++ b/mm/compaction.c
> @@ -2151,16 +2151,11 @@ static unsigned int fragmentation_score_zone_weighted(struct zone *zone)
> static unsigned int fragmentation_score_node(pg_data_t *pgdat)
> {
> unsigned int score = 0;
> + struct zone *zone;
> int zoneid;
>
> - for (zoneid = 0; zoneid < MAX_NR_ZONES; zoneid++) {
> - struct zone *zone;
> -
> - zone = &pgdat->node_zones[zoneid];
> - if (!populated_zone(zone))
> - continue;
> + for_each_populated_zone_pgdat(zone, pgdat)
> score += fragmentation_score_zone_weighted(zone);
> - }
>
> return score;
> }
next prev parent reply other threads:[~2024-03-14 7:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 0:54 [PATCH 0/3] mm: random cleanups Luis Chamberlain
2024-03-14 0:54 ` [PATCH 1/3] mm/show_mem: simplify ifdef on si_meminfo_node() Luis Chamberlain
2024-03-14 1:13 ` Kefeng Wang
2024-03-14 0:54 ` [PATCH 2/3] mm/compaction: add and use for_each_populated_zone_pgdat() helper Luis Chamberlain
2024-03-14 7:19 ` Baolin Wang [this message]
2024-03-15 5:38 ` Luis Chamberlain
2024-03-15 9:39 ` Baolin Wang
2024-03-15 11:09 ` Vlastimil Babka
2024-03-15 17:48 ` Luis Chamberlain
2024-03-14 11:40 ` kernel test robot
2024-03-14 0:54 ` [PATCH 3/3] mm/vmstat: simplfy extfrag_show_print with fragmentation_index() Luis Chamberlain
2024-03-15 11:13 ` Vlastimil Babka
2024-03-15 14:36 ` Davidlohr Bueso
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=ea5d5bb6-32a5-4161-95cd-3dc916576bf7@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=da.gomez@samsung.com \
--cc=dave@stgolabs.net \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=mgorman@suse.de \
--cc=p.raghav@samsung.com \
--cc=vbabka@suse.cz \
/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