From: David Hildenbrand <david@redhat.com>
To: "Huang, Ying" <ying.huang@intel.com>, Barry Song <21cnbao@gmail.com>
Cc: akpm@linux-foundation.org, shuah@kernel.org, linux-mm@kvack.org,
ryan.roberts@arm.com, chrisl@kernel.org, hughd@google.com,
kaleshsingh@google.com, kasong@tencent.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
Barry Song <v-songbaohua@oppo.com>
Subject: Re: [PATCH] selftests/mm: Introduce a test program to assess swap entry allocation for thp_swapout
Date: Thu, 20 Jun 2024 09:20:43 +0200 [thread overview]
Message-ID: <3e185f8d-da63-4a61-9cd1-9804bd972515@redhat.com> (raw)
In-Reply-To: <87zfrg2xce.fsf@yhuang6-desk2.ccr.corp.intel.com>
On 20.06.24 03:53, Huang, Ying wrote:
> Barry Song <21cnbao@gmail.com> writes:
>
>> From: Barry Song <v-songbaohua@oppo.com>
>>
>> Both Ryan and Chris have been utilizing the small test program to aid
>> in debugging and identifying issues with swap entry allocation. While
>> a real or intricate workload might be more suitable for assessing the
>> correctness and effectiveness of the swap allocation policy, a small
>> test program presents a simpler means of understanding the problem and
>> initially verifying the improvements being made.
>>
>> Let's endeavor to integrate it into the self-test suite. Although it
>> presently only accommodates 64KB and 4KB, I'm optimistic that we can
>> expand its capabilities to support multiple sizes and simulate more
>> complex systems in the future as required.
>
> IIUC, this is a performance test program instead of functionality test
> program. Does it match the purpose of the kernel selftest?
We do have the similar tests at least for ksm (ksm_tests.c) and probably
others:
$ git grep -l clock_gettime
ksm_tests.c
migration.c
mremap_test.c
transhuge-stress.c
I recall that gup_test.c also measures performance things.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-06-20 7:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 0:26 Barry Song
2024-06-20 1:53 ` Huang, Ying
2024-06-20 2:04 ` Barry Song
2024-06-20 5:20 ` Huang, Ying
2024-06-20 6:09 ` Barry Song
2024-06-20 6:34 ` Huang, Ying
2024-06-20 7:25 ` Barry Song
2024-06-20 7:59 ` Huang, Ying
2024-06-20 8:11 ` Barry Song
2024-06-20 8:26 ` Huang, Ying
2024-06-20 9:07 ` Barry Song
2024-06-20 7:20 ` David Hildenbrand [this message]
2024-06-20 7:24 ` Huang, Ying
2024-06-20 9:04 ` Ryan Roberts
2024-06-20 11:34 ` David Hildenbrand
2024-06-21 2:33 ` Huang, Ying
2024-06-21 7:25 ` Ryan Roberts
2024-06-21 7:47 ` Barry Song
2024-06-21 7:58 ` Ryan Roberts
2024-06-21 8:50 ` Chris Li
2024-06-21 11:20 ` Barry Song
2024-06-21 9:22 ` Huang, Ying
2024-06-21 9:43 ` Barry Song
2024-06-24 3:42 ` Huang, Ying
2024-06-24 4:05 ` Barry Song
2024-06-24 6:59 ` Huang, Ying
2024-06-24 7:55 ` Barry Song
2024-06-21 8:52 ` David Hildenbrand
2024-06-20 23:34 ` Chris Li
2024-06-21 7:34 ` Ryan Roberts
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=3e185f8d-da63-4a61-9cd1-9804bd972515@redhat.com \
--to=david@redhat.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chrisl@kernel.org \
--cc=hughd@google.com \
--cc=kaleshsingh@google.com \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
--cc=v-songbaohua@oppo.com \
--cc=ying.huang@intel.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
all inboxes | Powered by JetHome®