From: David Hildenbrand <david@redhat.com>
To: John Hubbard <jhubbard@nvidia.com>,
Ryan Roberts <ryan.roberts@arm.com>,
Mel Gorman <mgorman@techsingularity.net>,
linux-mm <linux-mm@kvack.org>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: NUMA + THP test suites?
Date: Tue, 31 Oct 2023 11:28:58 +0100 [thread overview]
Message-ID: <6064a18e-4fc7-47d6-ad83-f33585c96cd8@redhat.com> (raw)
In-Reply-To: <21812f89-c1a0-4ca0-9f73-54f20c4d29ef@nvidia.com>
On 31.10.23 00:21, John Hubbard wrote:
> Hi,
>
> I have some tentative solutions to the "NUMA balancing prerequisite" for
> Ryan's "[PATCH v6 0/9] variable-order, large folios for anonymous
> memory" [1]. However, I need to actually exercise the patches, in order
> to post anything worth reading, and as usual that is the hard part.
>
> After some initial searching around, it's time to simply ask: are there
> any test suites that will exercise NUMA page faults with THP? I am
> seeing hints of coverage, but with NUMA and THP separately covered, in
> the mm selftests. And also stress-ng has some numa coverage.
>
> So I was thinking of augmenting the selftests to get coverage (and the
> pte-mapped THP would be a happier story with this as well), but maybe
> tests along these lines already exist somewhere?
I suspect that you can run the autonuma-benchmark [1] (not sure if the
official repository) with THP enabled.
[1] https://github.com/pholasek/autonuma-benchmark
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2023-10-31 10:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 23:21 John Hubbard
2023-10-31 10:28 ` David Hildenbrand [this message]
2023-10-31 17:52 ` John Hubbard
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=6064a18e-4fc7-47d6-ad83-f33585c96cd8@redhat.com \
--to=david@redhat.com \
--cc=jhubbard@nvidia.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=ryan.roberts@arm.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