From: Wei Yang <richard.weiyang@gmail.com>
To: akpm@linux-foundation.org, mgorman@techsingularity.net, mhocko@suse.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Wei Yang <richard.weiyang@gmail.com>
Subject: [PATCH] mm/memory_hotplug: build zonelist for managed_zone
Date: Thu, 27 Jan 2022 01:20:23 +0000 [thread overview]
Message-ID: <20220127012023.18095-1-richard.weiyang@gmail.com> (raw)
During memory hotplug, when online/offline a zone, we need to rebuild
the zonelist for all node. There are two checks to decide whether a zone
would be added to zonelist:
* one in online_pages/offline_pages to decide necessity
* one in build_zonerefs_node to do real add
Currently we use different criteria at these two places, which is
different from the original behavior.
Originally during memory hotplug, zonelist is re-built when zone hasn't
been populated. This in introduced in 'commit 6811378e7d8b ("[PATCH]
wait_table and zonelist initializing for memory hotadd: update zonelists")'.
And at that moment, build_zonelists_node() also use populated_zone() to
decide whether the zone should be added to zonelist.
While in 'commit 6aa303defb74 ("mm, vmscan: only allocate and reclaim
from zones with pages managed by the buddy allocator")',
build_zonelists_node() changed to use managed_zone() to add zonelist.
But we still use populated_zone() to decide the necessity.
This patch restore the original behavior by using the same criteria to
add a zone in zonelist during memory hotplug.
Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
Fixes: 6aa303defb74 ("mm, vmscan: only allocate and reclaim from zones with pages managed by the buddy allocator")
CC: Mel Gorman <mgorman@techsingularity.net>
---
mm/memory_hotplug.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 2a9627dc784c..8f1906b33937 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -1102,11 +1102,11 @@ int __ref online_pages(unsigned long pfn, unsigned long nr_pages,
spin_unlock_irqrestore(&zone->lock, flags);
/*
- * If this zone is not populated, then it is not in zonelist.
+ * If this zone is not managed, then it is not in zonelist.
* This means the page allocator ignores this zone.
* So, zonelist must be updated after online.
*/
- if (!populated_zone(zone)) {
+ if (!managed_zone(zone)) {
need_zonelists_rebuild = 1;
setup_zone_pageset(zone);
}
@@ -1985,7 +1985,7 @@ int __ref offline_pages(unsigned long start_pfn, unsigned long nr_pages,
/* reinitialise watermarks and update pcp limits */
init_per_zone_wmark_min();
- if (!populated_zone(zone)) {
+ if (!managed_zone(zone)) {
zone_pcp_reset(zone);
build_all_zonelists(NULL);
}
--
2.33.1
next reply other threads:[~2022-01-27 1:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 1:20 Wei Yang [this message]
2022-01-27 8:28 ` Michal Hocko
2022-01-29 0:26 ` Wei Yang
2022-01-31 10:24 ` Michal Hocko
2022-02-01 6:33 ` Wei Yang
2022-01-27 8:39 ` David Hildenbrand
2022-01-29 0:27 ` Wei Yang
2022-01-31 10:53 ` David Hildenbrand
2022-02-01 7:00 ` Wei Yang
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=20220127012023.18095-1-richard.weiyang@gmail.com \
--to=richard.weiyang@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.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