linux-kernel - Re: [PATCH 0/2] Support kshrinkd

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: <ZdQUmWxYuuP24w_1@casper.infradead.org>
Date: Tue, 20 Feb 2024 02:55:21 +0000
From: Matthew Wilcox <willy@...radead.org>
To: 李培锋 <lipeifeng@...o.com>
Cc: akpm@...ux-foundation.org, david@...hat.com, osalvador@...e.de,
	linux-mm@...ck.org, linux-kernel@...r.kernel.org,
	v-songbaohua@...o.com, gregkh@...gle.com, tkjos@...gle.com
Subject: Re: [PATCH 0/2] Support kshrinkd

On Tue, Feb 20, 2024 at 10:04:33AM +0800, 李培锋 wrote:
> Monkey-test in phone with 16G-ram for 300 hours shows that almost one-third
> 
> of the contended-pages can be freed successfully next time, putting back
> those
> 
> folios to LRU's head would break the rules of inative-LRU.

You talk about "the rules of inactive LRU" like we care.  The LRU is
an approximation at best.  What are the *consequences*?  Is there a
benchmark that executes more operations per second as a result of
this patch?