From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Huang Ying <ying.huang@intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>,
Zi Yan <ziy@nvidia.com>, Oscar Salvador <osalvador@suse.de>,
Yang Shi <shy828301@gmail.com>,
zhongjiang-ali <zhongjiang-ali@linux.alibaba.com>,
Xunlei Pang <xlpang@linux.alibaba.com>
Subject: Re: [PATCH] mm,migrate: fix establishing demotion target
Date: Mon, 7 Feb 2022 09:38:44 +0800 [thread overview]
Message-ID: <07970c9c-9816-650b-26ab-ed9aa46d0653@linux.alibaba.com> (raw)
In-Reply-To: <20220128055940.1792614-1-ying.huang@intel.com>
On 1/28/2022 1:59 PM, Huang Ying wrote:
> In commit ac16ec835314 ("mm: migrate: support multiple target nodes
> demotion"), after the first demotion target node is found, we will
> continue to check the next candidate obtained via
> find_next_best_node(). This is to find all demotion target nodes with
> same NUMA distance. But one side effect of find_next_best_node() is
> that the candidate node returned will be set in "used" parameter, even
> if the candidate node isn't passed in the following NUMA distance
> checking, the candidate node will not be used as demotion target node
> for the following nodes. For example, for system as follows,
>
> node distances:
> node 0 1 2 3
> 0: 10 21 17 28
> 1: 21 10 28 17
> 2: 17 28 10 28
> 3: 28 17 28 10
>
> when we establish demotion target node for node 0, in the first round
> node 2 is added to the demotion target node set. Then in the second
> round, node 3 is checked and failed because distance(0, 3) >
> distance(0, 2). But node 3 is set in "used" nodemask too. When we
> establish demotion target node for node 1, there is no available node.
> This is wrong, node 3 should be set as the demotion target of node 1.
>
> To fix this, if the candidate node is failed to pass the distance
> checking, it will be cleared in "used" nodemask. So that it can be
> used for the following node.
>
> The bug can be reproduced and fixed with this patch on a 2 socket
> server machine with DRAM and PMEM.
>
> Fixes: ac16ec835314 ("mm: migrate: support multiple target nodes demotion")
> Signed-off-by: "Huang, Ying" <ying.huang@intel.com>
> Cc: Baolin Wang <baolin.wang@linux.alibaba.com>
> Cc: Dave Hansen <dave.hansen@linux.intel.com>
> Cc: Zi Yan <ziy@nvidia.com>
> Cc: Oscar Salvador <osalvador@suse.de>
> Cc: Yang Shi <shy828301@gmail.com>
> Cc: Baolin Wang <baolin.wang@linux.alibaba.com>
> Cc: zhongjiang-ali <zhongjiang-ali@linux.alibaba.com>
> Cc: Xunlei Pang <xlpang@linux.alibaba.com>
> ---
Good catch. Thanks.
Reviewed-by: Baolin Wang <baolin.wang@linux.alibaba.com>
> mm/migrate.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/mm/migrate.c b/mm/migrate.c
> index c7da064b4781..e8a6933af68d 100644
> --- a/mm/migrate.c
> +++ b/mm/migrate.c
> @@ -3082,18 +3082,21 @@ static int establish_migrate_target(int node, nodemask_t *used,
> if (best_distance != -1) {
> val = node_distance(node, migration_target);
> if (val > best_distance)
> - return NUMA_NO_NODE;
> + goto out_clear;
> }
>
> index = nd->nr;
> if (WARN_ONCE(index >= DEMOTION_TARGET_NODES,
> "Exceeds maximum demotion target nodes\n"))
> - return NUMA_NO_NODE;
> + goto out_clear;
>
> nd->nodes[index] = migration_target;
> nd->nr++;
>
> return migration_target;
> +out_clear:
> + node_clear(migration_target, *used);
> + return NUMA_NO_NODE;
> }
>
> /*
prev parent reply other threads:[~2022-02-07 1:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 5:59 Huang Ying
2022-02-07 1:38 ` Baolin Wang [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=07970c9c-9816-650b-26ab-ed9aa46d0653@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=shy828301@gmail.com \
--cc=xlpang@linux.alibaba.com \
--cc=ying.huang@intel.com \
--cc=zhongjiang-ali@linux.alibaba.com \
--cc=ziy@nvidia.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