From: Zi Yan <ziy@nvidia.com>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Donet Tom <donettom@linux.ibm.com>,
David Hildenbrand <david@redhat.com>, Dev Jain <dev.jain@arm.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Subject: Re: [Patch v2] selftests/mm: do check_huge_anon() with a number been passed in
Date: Mon, 11 Aug 2025 14:42:08 -0400 [thread overview]
Message-ID: <F08C69B5-9906-4FD9-899F-5CE6E725ACAC@nvidia.com> (raw)
In-Reply-To: <20250809194209.30484-1-richard.weiyang@gmail.com>
On 9 Aug 2025, at 15:42, Wei Yang wrote:
> Currently it hard codes the number of hugepage to check for
> check_huge_anon(), but it would be more reasonable to do the check based
> on a number passed in.
>
> Pass in the hugepage number and do the check based on it.
>
> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
> Cc: Baolin Wang <baolin.wang@linux.alibaba.com>
> Cc: Donet Tom <donettom@linux.ibm.com>
> Cc: David Hildenbrand <david@redhat.com>
> Cc: Dev Jain <dev.jain@arm.com>
> Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> Cc: Zi Yan <ziy@nvidia.com>
>
> ---
> v2:
> * use mm-new
> * add back nr_hpages which is removed by an early commit
> * adjust the change log a little
> * drop RB and resend
> ---
> tools/testing/selftests/mm/split_huge_page_test.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
LGTM. Reviewed-by: Zi Yan <ziy@nvidia.com>
Best Regards,
Yan, Zi
next prev parent reply other threads:[~2025-08-11 18:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-09 19:42 Wei Yang
2025-08-10 13:37 ` Donet Tom
2025-08-11 0:53 ` Wei Yang
2025-08-11 1:48 ` Donet Tom
2025-08-11 5:58 ` Baolin Wang
2025-08-11 8:00 ` David Hildenbrand
2025-08-11 18:42 ` Zi Yan [this message]
2025-08-11 20:08 ` Vishal Moola (Oracle)
2025-08-12 2:26 ` wang lian
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=F08C69B5-9906-4FD9-899F-5CE6E725ACAC@nvidia.com \
--to=ziy@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=donettom@linux.ibm.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=richard.weiyang@gmail.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