lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d0b20f47-384d-49f1-8449-0da6da11089c@redhat.com>
Date: Thu, 20 Jun 2024 13:34:02 +0200
From: David Hildenbrand <david@...hat.com>
To: Ryan Roberts <ryan.roberts@....com>, Barry Song <21cnbao@...il.com>,
 akpm@...ux-foundation.org, shuah@...nel.org, linux-mm@...ck.org
Cc: chrisl@...nel.org, hughd@...gle.com, kaleshsingh@...gle.com,
 kasong@...cent.com, linux-kernel@...r.kernel.org, ying.huang@...el.com,
 linux-kselftest@...r.kernel.org, Barry Song <v-songbaohua@...o.com>
Subject: Re: [PATCH] selftests/mm: Introduce a test program to assess swap
 entry allocation for thp_swapout

On 20.06.24 11:04, Ryan Roberts wrote:
> On 20/06/2024 01:26, Barry Song wrote:
>> From: Barry Song <v-songbaohua@...o.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.
> 
> I'll try to summarize the thread with Huang Ying by suggesting this test program
> is "neccessary but not sufficient" to exhaustively test the mTHP swap-out path.
> I've certainly found it useful and think it would be a valuable addition to the
> tree.
> 
> That said, I'm not convinced it is a selftest; IMO a selftest should provide a
> clear pass/fail result against some criteria and must be able to be run
> automatically by (e.g.) a CI system.

Likely we should then consider moving other such performance-related 
thingies out of the selftests?

-- 
Cheers,

David / dhildenb


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ