From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: Hao Li <hao.li@linux.dev>, Joshua Hahn <joshua.hahnjy@gmail.com>
Cc: david@kernel.org, osalvador@suse.de, akpm@linux-foundation.org,
vbabka@suse.cz, harry.yoo@oracle.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-cxl@vger.kernel.org
Subject: Re: [PATCH] mm/memory_hotplug: maintain N_NORMAL_MEMORY during hotplug
Date: Mon, 30 Mar 2026 13:43:57 +0200 [thread overview]
Message-ID: <837fe882-0d42-47eb-9234-9d5787148650@kernel.org> (raw)
In-Reply-To: <onaszvpegcqt2y3domgplkne5wrpk7iibgj3mybx4wvckqwe5f@qrnlhiksef4b>
On 3/28/26 05:03, Hao Li wrote:
> On Fri, Mar 27, 2026 at 09:35:54AM -0700, Joshua Hahn wrote:
>> On Fri, 27 Mar 2026 15:44:18 +0100 "Vlastimil Babka (SUSE)" <vbabka@kernel.org> wrote:
>>
>> > >> 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.
>> >
>> > But commit 8d2882a8edb8 didn't introduce the current state, or did it?
>>
>> I don't mean to speak on Hao's behalf, but as far as I can tell I think this
>> would have been the commit to introduce the state, since
>> node_states_check_changes_online would set status_change_nid_normal to nid,
>> then nodes_states_set_node would come around and set it to N_NORMAL_MEMORY.
>> Maybe I'm missing something? :0
>
> Thanks for this analysis. I was thinking the same. N_NORMAL_MEMORY is no longer
> updated after this commit.
You're right. Initially I found a much older commit that seemed to remove
updating N_NORMAL_MEMORY shortly after it was introduced. But seems it was
reintroduced later and indeed 8d2882a8edb8 removed it again. Partially my
fault as I reviewed that commit and was blind to that aspect - that it's not
just removing an unused status_change_nid_normal. Thanks for figuring that out!
>>
>> Thanks for the reply, Vlastimil. I hope you have a great day : -)
>> Joshua
>
next prev parent reply other threads:[~2026-03-30 11:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 12:42 Hao Li
2026-03-27 14:38 ` Joshua Hahn
2026-03-27 14:44 ` Vlastimil Babka (SUSE)
2026-03-27 15:22 ` David Hildenbrand (Arm)
2026-03-28 4:09 ` Hao Li
2026-03-27 16:35 ` Joshua Hahn
2026-03-28 4:03 ` Hao Li
2026-03-30 11:43 ` Vlastimil Babka (SUSE) [this message]
2026-03-27 15:28 ` David Hildenbrand (Arm)
2026-03-28 4:12 ` Hao Li
2026-03-28 3:47 ` Hao Li
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=837fe882-0d42-47eb-9234-9d5787148650@kernel.org \
--to=vbabka@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=hao.li@linux.dev \
--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