From: Ingo Molnar <mingo@kernel.org>
To: Qi Zheng <zhengqi.arch@bytedance.com>
Cc: akpm@linux-foundation.org, rppt@kernel.org, david@redhat.com,
vbabka@suse.cz, mhocko@suse.com, willy@infradead.org,
mgorman@techsingularity.net, 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 v3 1/2] mm: page_alloc: skip memoryless nodes entirely
Date: Fri, 20 Oct 2023 10:31:08 +0200 [thread overview]
Message-ID: <ZTI6zM0MUlfglkD+@gmail.com> (raw)
In-Reply-To: <157013e978468241de4a4c05d5337a44638ecb0e.1697711415.git.zhengqi.arch@bytedance.com>
* Qi Zheng <zhengqi.arch@bytedance.com> wrote:
> In find_next_best_node(), We skipped the memoryless nodes
s/We
/we
s/the memoryless nodes
/memoryless nodes
> when building the zonelists of other normal nodes (N_NORMAL),
> but did not skip the memoryless node itself when building
> the zonelist. This will cause it to be traversed at runtime.
>
> For example, say we have node0 and node1, node0 is memoryless
> node, then the fallback order of node0 and node1 as follows:
>
> [ 0.153005] Fallback order for Node 0: 0 1
> [ 0.153564] Fallback order for Node 1: 1
>
> After this patch, we skip memoryless node0 entirely, then
> the fallback order of node0 and node1 as follows:
s/fallback
/fall back
>
> [ 0.155236] Fallback order for Node 0: 1
> [ 0.155806] Fallback order for Node 1: 1
>
> So it becomes completely invisible, which will reduce runtime
> overhead.
>
> And in this way, we will not try to allocate pages from memoryless
> node0, then the panic mentioned in [1] will also be fixed. Even though
> this problem has been solved by dropping the NODE_MIN_SIZE constrain
> in x86 [2], it would be better to fix it in core MM as well.
s/in core MM
/in the core MM
> [1]. https://lore.kernel.org/all/20230212110305.93670-1-zhengqi.arch@bytedance.com/
> [2]. https://lore.kernel.org/all/20231017062215.171670-1-rppt@kernel.org/
>
> Signed-off-by: Qi Zheng <zhengqi.arch@bytedance.com>
> Acked-by: David Hildenbrand <david@redhat.com>
> + /*
> + * Use the local node if we haven't already. But for memoryless local
> + * node, we should skip it and fallback to other nodes.
s/fallback
/fall back
s/already. But
/already, but
Acked-by: Ingo Molnar <mingo@kernel.org>
Thanks,
Ingo
next prev parent reply other threads:[~2023-10-20 8:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 10:43 [PATCH v3 0/2] handle memoryless nodes more appropriately Qi Zheng
2023-10-19 10:43 ` [PATCH v3 1/2] mm: page_alloc: skip memoryless nodes entirely Qi Zheng
2023-10-20 8:31 ` Ingo Molnar [this message]
2023-10-20 9:09 ` Qi Zheng
2023-10-19 10:43 ` [PATCH v3 2/2] mm: memory_hotplug: drop memoryless node from fallback lists Qi Zheng
2023-10-20 7:05 ` Huang, Ying
2023-10-20 7:35 ` Qi Zheng
2023-10-23 1:18 ` Huang, Ying
2023-10-23 2:53 ` Qi Zheng
2023-10-23 3:10 ` Huang, Ying
2023-10-23 3:17 ` Qi Zheng
2023-10-23 18:19 ` Andrew Morton
2023-10-20 8:32 ` Ingo Molnar
2023-10-20 9:10 ` 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=ZTI6zM0MUlfglkD+@gmail.com \
--to=mingo@kernel.org \
--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=osalvador@suse.de \
--cc=rppt@kernel.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=ying.huang@intel.com \
--cc=zhengqi.arch@bytedance.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;
as well as URLs for NNTP newsgroup(s).