From: Andrew Morton <akpm@linux-foundation.org>
To: Yuntao Wang <yuntao.wang@linux.dev>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH] mm/page_alloc: Remove the incorrect and misleading comment
Date: Wed, 15 Jan 2025 15:42:43 -0800 [thread overview]
Message-ID: <20250115154243.4a31f9fbf805169d2c5594dd@linux-foundation.org> (raw)
In-Reply-To: <20250115041634.63387-1-yuntao.wang@linux.dev>
On Wed, 15 Jan 2025 12:16:34 +0800 Yuntao Wang <yuntao.wang@linux.dev> wrote:
> The comment removed in this patch originally belonged to the
> build_zonelists_in_zone_order() function, which was introduced by commit
> f0c0b2b808f2 ("change zonelist order: zonelist order selection logic").
>
> Later, commit c9bff3eebc09 ("mm, page_alloc: rip out ZONELIST_ORDER_ZONE")
> removed build_zonelists_in_zone_order() but left its comment behind.
>
> Subsequently, commit 9d3be21bf9c0 ("mm, page_alloc: simplify zonelist
> initialization") moved the node_order variable into build_zonelists(),
> making the comment originally belonged to build_zonelists_in_zone_order()
> appear as if it were part of build_zonelists().
>
> ...
>
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -5161,13 +5161,6 @@ static void build_thisnode_zonelists(pg_data_t *pgdat)
> zonerefs->zone_idx = 0;
> }
>
> -/*
> - * Build zonelists ordered by zone and nodes within zones.
> - * This results in conserving DMA zone[s] until all Normal memory is
> - * exhausted, but results in overflowing to remote node while memory
> - * may still exist in local DMA zone.
> - */
> -
Yes, it's not obvious which code this comment is telling us about.
I do wonder if the information in this comment could be updated and
moved somewhere more appropriate, rather than simply removing it. Oh
well, not very important.
prev parent reply other threads:[~2025-01-15 23:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 4:16 Yuntao Wang
2025-01-15 23:42 ` Andrew Morton [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=20250115154243.4a31f9fbf805169d2c5594dd@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=yuntao.wang@linux.dev \
/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