From: Mike Rapoport <rppt@kernel.org>
To: Sang-Heon Jeon <ekffu200098@gmail.com>
Cc: akpm@linux-foundation.org, djbw@kernel.org, mingo@kernel.org,
linux-mm@kvack.org, Donghyeon Lee <asd142513@gmail.com>,
Munhui Chae <mochae@student.42seoul.kr>
Subject: Re: [PATCH v2] mm/fake-numa: fix under-allocation detection in uniform split
Date: Mon, 20 Apr 2026 09:31:04 +0300 [thread overview]
Message-ID: <aeXIKM9BeRmaCZ_d@kernel.org> (raw)
In-Reply-To: <20260417135805.1758378-1-ekffu200098@gmail.com>
Hi,
On Fri, Apr 17, 2026 at 10:58:05PM +0900, Sang-Heon Jeon wrote:
> When split NUMA node uniformly, split_nodes_size_interleave_uniform()
> returns the next absolute node ID, not the number of nodes created.
>
> The existing under-allocation detection logic compares next absolute node
> ID (ret) and request count (n), which only works when nid starts at 0.
>
> For example, on a system with 2 physical NUMA nodes (node 0: 2GB, node
> 1: 128MB) and numa=fake=8U, 8 fake nodes are successfully created from
> node 0 and split_nodes_size_interleave_uniform() returns 8. For node 1,
> fake node nid starts at 8, but only 4 fake nodes are created due to
> current FAKE_NODE_MIN_SIZE being 32MB, and
> split_nodes_size_interleave_uniform() returns 12. By existing
> under-allocation detection logic, "ret < n" (12 < 8) is false, so the
In this example it would be 11, won't it?
I'll update when applying.
> under-allocation will not be detected.
>
> Fix under-allocation detection logic to compare the number of actually
> created nodes (ret - nid) against the request count (n). Also skip
> under-allocation detection logic for memoryless physical nodes where no
> fake nodes are created.
>
> Also, fix the outdated comment to match the actual return value.
>
> Signed-off-by: Sang-Heon Jeon <ekffu200098@gmail.com>
> Reported-by: Donghyeon Lee <asd142513@gmail.com>
> Reported-by: Munhui Chae <mochae@student.42seoul.kr>
> Fixes: cc9aec03e58f ("x86/numa_emulation: Introduce uniform split capability") # 4.19
...
> @@ -416,9 +416,18 @@ void __init numa_emulation(struct numa_meminfo *numa_meminfo, int numa_dist_cnt)
> n, &pi.blk[0], nid);
> if (ret < 0)
> break;
> - if (ret < n) {
> +
> + /*
> + * If no memory was found for this physical node,
> + * skip the under-allocation check.
checkpatch complains about trailing white space here.
I'll fix it up when applying.
> + */
> + if (ret == nid)
> + continue;
> +
> + nr_created = ret - nid;
> + if (nr_created < n) {
> pr_info("%s: phys: %d only got %d of %ld nodes, failing\n",
> - __func__, i, ret, n);
> + __func__, i, nr_created, n);
> ret = -1;
> break;
> }
> --
> 2.43.0
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-04-20 6:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 13:58 Sang-Heon Jeon
2026-04-20 6:31 ` Mike Rapoport [this message]
2026-04-20 13:50 ` Sang-Heon Jeon
2026-04-20 14:26 ` Sang-Heon Jeon
2026-04-21 6:29 ` Mike Rapoport
2026-04-21 6:56 ` Sang-Heon Jeon
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=aeXIKM9BeRmaCZ_d@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=asd142513@gmail.com \
--cc=djbw@kernel.org \
--cc=ekffu200098@gmail.com \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=mochae@student.42seoul.kr \
/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