linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hao Li <hao.li@linux.dev>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: osalvador@suse.de, akpm@linux-foundation.org, vbabka@suse.cz,
	 harry.yoo@oracle.com, joshua.hahnjy@gmail.com,
	linux-mm@kvack.org,  linux-kernel@vger.kernel.org,
	linux-cxl@vger.kernel.org
Subject: Re: [PATCH v2] mm/memory_hotplug: maintain N_NORMAL_MEMORY during hotplug
Date: Tue, 31 Mar 2026 12:14:14 +0800	[thread overview]
Message-ID: <lj2h4mig2za32bi5gnxmeh7gjshd2gwa45zl3xhot4cjsvtwsv@5jjtp2el3yn5> (raw)
In-Reply-To: <5de08585-fd2b-4395-b421-99c7b887aa8f@kernel.org>

On Mon, Mar 30, 2026 at 04:20:23PM +0200, David Hildenbrand (Arm) wrote:
> On 3/30/26 05:57, Hao Li wrote:
> > N_NORMAL_MEMORY is initialized from zone population at boot, but memory
> > hotplug currently only updates N_MEMORY. As a result, a node that gains
> > normal memory via hotplug can remain invisible to users iterating over
> > N_NORMAL_MEMORY, while a node that loses its last normal memory can stay
> > incorrectly marked as such.
> > 
> > Restore N_NORMAL_MEMORY maintenance directly in online_pages() and
> > offline_pages(). Set the bit when a node that currently lacks normal
> > memory onlines pages into a zone <= ZONE_NORMAL, and clear it when
> > offlining removes the last present pages from zones <= ZONE_NORMAL.
> > 
> > This restores the intended semantics without bringing back the old
> > status_change_nid_normal notifier plumbing which was removed in
> > 8d2882a8edb8.
> > 
> > Current users that benefit include list_lru, zswap, nfsd filecache,
> > hugetlb_cgroup, and has_normal_memory sysfs reporting.
> > 
> > Fixes: 8d2882a8edb8 ("mm,memory_hotplug: remove status_change_nid_normal and update documentation")
> 
> Agreed on CCing stable.
> 
> > Signed-off-by: Hao Li <hao.li@linux.dev>
> > ---
> > Changes: simplify the code. (Thanks Joshua and David)
> > ---
> >  mm/memory_hotplug.c | 20 ++++++++++++++++++++
> >  1 file changed, 20 insertions(+)
> > 
> > diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
> > index bc805029da51..05a47953ef21 100644
> > --- a/mm/memory_hotplug.c
> > +++ b/mm/memory_hotplug.c
> > @@ -1209,6 +1209,13 @@ int online_pages(unsigned long pfn, unsigned long nr_pages,
> >  
> >  	if (node_arg.nid >= 0)
> >  		node_set_state(nid, N_MEMORY);
> > +	/*
> > +	 * Check whether we are adding normal memory to the node for the first
> > +	 * time.
> > +	 */
> > +	if (!node_state(nid, N_NORMAL_MEMORY) && zone_idx(zone) <= ZONE_NORMAL)
> > +		node_set_state(nid, N_NORMAL_MEMORY);
> > +
> >  	if (need_zonelists_rebuild)
> >  		build_all_zonelists(NULL);
> >  
> > @@ -1908,6 +1915,8 @@ int offline_pages(unsigned long start_pfn, unsigned long nr_pages,
> >  	unsigned long flags;
> >  	char *reason;
> >  	int ret;
> > +	unsigned long normal_pages = 0;
> > +	enum zone_type zt;
> >  
> >  	/*
> >  	 * {on,off}lining is constrained to full memory sections (or more
> > @@ -2055,6 +2064,17 @@ int offline_pages(unsigned long start_pfn, unsigned long nr_pages,
> >  	/* reinitialise watermarks and update pcp limits */
> >  	init_per_zone_wmark_min();
> >  
> > +	/*
> > +	 * Check whether this operation removes the last normal memory from
> > +	 * the node. We do this before clearing N_MEMORY to avoid the possible
> > +	 * transient "!N_MEMORY && N_NORMAL_MEMORY" state.
> > +	 */
> > +	if (zone_idx(zone) <= ZONE_NORMAL) {
> > +		for (zt = 0; zt <= ZONE_NORMAL; zt++)
> > +			normal_pages += pgdat->node_zones[zt].present_pages;
> > +		if (!normal_pages)
> > +			node_clear_state(node, N_NORMAL_MEMORY);
> > +	}
> 
> Was wondering whether we could just do an early exit, like:
> 
> 
> for (zt = 0; zt <= ZONE_NORMAL; zt++) {
> 	if (pgdat->node_zones[zt].present_pages)
> 		break;
> }
> if (zt > ZONE_NORMAL)
> 	node_clear_state(node, N_NORMAL_MEMORY);
> 
> But ends up being harder to digest (incl. all variants I tried :) ), so

Thanks for exploring this.
Yeah, this looks like one of those cases where we have to make a bit of a
tradeoff for readability :)

> 
> Acked-by: David Hildenbrand (Arm) <david@kernel.org>

Thanks for the Ack!

-- 
Thanks,
Hao


      reply	other threads:[~2026-03-31  4:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30  3:57 Hao Li
2026-03-30  8:28 ` Harry Yoo (Oracle)
2026-03-30  9:34   ` Hao Li
2026-03-30 21:46     ` Andrew Morton
2026-03-31  4:24       ` Hao Li
2026-03-31  5:15         ` Andrew Morton
2026-03-30 12:07 ` Vlastimil Babka (SUSE)
2026-03-30 13:53 ` Joshua Hahn
2026-03-30 14:20 ` David Hildenbrand (Arm)
2026-03-31  4:14   ` Hao Li [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=lj2h4mig2za32bi5gnxmeh7gjshd2gwa45zl3xhot4cjsvtwsv@5jjtp2el3yn5 \
    --to=hao.li@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=harry.yoo@oracle.com \
    --cc=joshua.hahnjy@gmail.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=osalvador@suse.de \
    --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