From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Feng Tang <feng.tang@linux.alibaba.com>,
Andrew Morton <akpm@linux-foundation.org>,
Shuah Khan <shuah@kernel.org>,
Sri Jayaramappa <sjayaram@akamai.com>,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] selftests/mm: compaction_test: Support platform with huge mount of memory
Date: Thu, 24 Apr 2025 14:28:33 +0800 [thread overview]
Message-ID: <da797800-7172-429f-bfe7-87bdec82f2bb@linux.alibaba.com> (raw)
In-Reply-To: <20250423103645.2758-1-feng.tang@linux.alibaba.com>
On 2025/4/23 18:36, Feng Tang wrote:
> When running mm selftest to verify mm patches, 'compaction_test' case
> failed on an x86 server with 1TB memory. And the root cause is that it
> has too much free memory than what the test supports.
>
> The test case tries to allocate 100000 huge pages, which is about 200 GB
> for that x86 server, and when it succeeds, it expects it's large than
> 1/3 of 80% of the free memory in system. This logic only works for
> platform with 750 GB ( 200 / (1/3) / 80% ) or less free memory, and may
> raise false alarm for others.
>
> Fix it by changing the fixed page number to self-adjustable number
> according to the real number of free memory.
>
> Fixes: bd67d5c15cc19 ("Test compaction of mlocked memory")
> Signed-off-by: Feng Tang <feng.tang@linux.alibaba.com>
Make sense to me. I tested it and passed on my platform. So:
Reviewed-by: Baolin Wang <baolin.wang@linux.alibaba.com>
Tested-by: Baolin Wang <baolin.wang@inux.alibaba.com>
> ---
> tools/testing/selftests/mm/compaction_test.c | 19 ++++++++++++++-----
> 1 file changed, 14 insertions(+), 5 deletions(-)
>
> diff --git a/tools/testing/selftests/mm/compaction_test.c b/tools/testing/selftests/mm/compaction_test.c
> index 2c3a0eb6b22d..9bc4591c7b16 100644
> --- a/tools/testing/selftests/mm/compaction_test.c
> +++ b/tools/testing/selftests/mm/compaction_test.c
> @@ -90,6 +90,8 @@ int check_compaction(unsigned long mem_free, unsigned long hugepage_size,
> int compaction_index = 0;
> char nr_hugepages[20] = {0};
> char init_nr_hugepages[24] = {0};
> + char target_nr_hugepages[24] = {0};
> + int slen;
>
> snprintf(init_nr_hugepages, sizeof(init_nr_hugepages),
> "%lu", initial_nr_hugepages);
> @@ -106,11 +108,18 @@ int check_compaction(unsigned long mem_free, unsigned long hugepage_size,
> goto out;
> }
>
> - /* Request a large number of huge pages. The Kernel will allocate
> - as much as it can */
> - if (write(fd, "100000", (6*sizeof(char))) != (6*sizeof(char))) {
> - ksft_print_msg("Failed to write 100000 to /proc/sys/vm/nr_hugepages: %s\n",
> - strerror(errno));
> + /*
> + * Request huge pages for about half of the free memory. The Kernel
> + * will allocate as much as it can, and we expect it will get at least 1/3
> + */
> + nr_hugepages_ul = mem_free / hugepage_size / 2;
> + snprintf(target_nr_hugepages, sizeof(target_nr_hugepages),
> + "%lu", nr_hugepages_ul);
> +
> + slen = strlen(target_nr_hugepages);
> + if (write(fd, target_nr_hugepages, slen) != slen) {
> + ksft_print_msg("Failed to write %lu to /proc/sys/vm/nr_hugepages: %s\n",
> + nr_hugepages_ul, strerror(errno));
> goto close_fd;
> }
>
prev parent reply other threads:[~2025-04-24 6:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 10:36 Feng Tang
2025-04-23 11:03 ` Dev Jain
2025-04-24 1:22 ` Feng Tang
2025-04-24 6:28 ` 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=da797800-7172-429f-bfe7-87bdec82f2bb@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=feng.tang@linux.alibaba.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shuah@kernel.org \
--cc=sjayaram@akamai.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