From: Qi Zheng <zhengqi.arch@bytedance.com>
To: David Hildenbrand <david@redhat.com>
Cc: akpm@linux-foundation.org, rppt@kernel.org, vbabka@suse.cz,
mhocko@suse.com, willy@infradead.org,
mgorman@techsingularity.net, mingo@kernel.org,
aneesh.kumar@linux.ibm.com, ying.huang@intel.com,
hannes@cmpxchg.org, osalvador@suse.de,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v2 2/2] mm: memory_hotplug: drop memoryless node from fallback lists
Date: Thu, 19 Oct 2023 16:22:38 +0800 [thread overview]
Message-ID: <b7bca04e-0665-f80a-94b6-b8d857edfce1@bytedance.com> (raw)
In-Reply-To: <66e16a28-2d04-4b2c-88a8-692edf587f02@redhat.com>
Hi David,
On 2023/10/19 16:11, David Hildenbrand wrote:
> On 19.10.23 09:36, Qi Zheng wrote:
>> In offline_pages(), if a node becomes memoryless, we
>> will clear its N_MEMORY state by calling node_states_clear_node().
>> But we do this after rebuilding the zonelists by calling
>> build_all_zonelists(), which will cause this memoryless node to
>> still be in the fallback list of other nodes. This will incur
>> some runtime overhead.
>>
>> To drop memoryless node from fallback lists in this case, just
>> call node_states_clear_node() before calling build_all_zonelists().
>>
>> Signed-off-by: Qi Zheng <zhengqi.arch@bytedance.com>
>> ---
>> mm/memory_hotplug.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
>> index d4a364fdaf8f..18af399627f0 100644
>> --- a/mm/memory_hotplug.c
>> +++ b/mm/memory_hotplug.c
>> @@ -2036,12 +2036,12 @@ int __ref offline_pages(unsigned long
>> start_pfn, unsigned long nr_pages,
>> /* reinitialise watermarks and update pcp limits */
>> init_per_zone_wmark_min();
>> + node_states_clear_node(node, &arg);
>> if (!populated_zone(zone)) {
>> zone_pcp_reset(zone);
>> build_all_zonelists(NULL);
>> }
>> - node_states_clear_node(node, &arg);
>> if (arg.status_change_nid >= 0) {
>> kcompactd_stop(node);
>> kswapd_stop(node);
>
> Probably worth a comment.
>
> /*
> * Make sure to mark the node as memory-less before rebuilding the zone
> * list. Otherwise this node would still appear in the fallback lists.
> */
OK, will add it in the v3.
>
> Acked-by: David Hildenbrand <david@redhat.com>
Thanks.
>
next prev parent reply other threads:[~2023-10-19 8:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 7:36 [PATCH v2 0/2] handle memoryless nodes more appropriately Qi Zheng
2023-10-19 7:36 ` [PATCH v2 1/2] mm: page_alloc: skip memoryless nodes entirely Qi Zheng
2023-10-19 8:07 ` David Hildenbrand
2023-10-19 8:21 ` Qi Zheng
2023-10-19 7:36 ` [PATCH v2 2/2] mm: memory_hotplug: drop memoryless node from fallback lists Qi Zheng
2023-10-19 8:11 ` David Hildenbrand
2023-10-19 8:22 ` Qi Zheng [this message]
2023-10-19 7:56 ` [PATCH v2 0/2] handle memoryless nodes more appropriately David Hildenbrand
2023-10-19 8:17 ` Qi Zheng
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=b7bca04e-0665-f80a-94b6-b8d857edfce1@bytedance.com \
--to=zhengqi.arch@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=osalvador@suse.de \
--cc=rppt@kernel.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=ying.huang@intel.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