From: Matthew Wilcox <willy@infradead.org>
To: 李培锋 <lipeifeng@oppo.com>
Cc: akpm@linux-foundation.org, david@redhat.com, osalvador@suse.de,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
v-songbaohua@oppo.com, gregkh@google.com, tkjos@google.com
Subject: Re: [PATCH 0/2] Support kshrinkd
Date: Tue, 20 Feb 2024 02:55:21 +0000 [thread overview]
Message-ID: <ZdQUmWxYuuP24w_1@casper.infradead.org> (raw)
In-Reply-To: <a642d9dc-6d48-016c-7007-c08ce8933d18@oppo.com>
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?
next prev parent reply other threads:[~2024-02-20 2:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 14:17 lipeifeng
2024-02-19 14:17 ` [PATCH 2/2] mm: support kshrinkd lipeifeng
2024-02-20 2:11 ` 李培锋
2024-02-20 3:19 ` Barry Song
2024-02-19 16:51 ` [PATCH 0/2] Support kshrinkd Matthew Wilcox
2024-02-20 2:04 ` 李培锋
2024-02-20 2:55 ` Matthew Wilcox [this message]
2024-02-20 4:14 ` 李培锋
[not found] ` <20240219141703.3851-2-lipeifeng@oppo.com>
2024-02-20 1:42 ` [PATCH 1/2] mm/rmap: support folio_referenced to control if try_lock in rmap_walk 李培锋
2024-02-20 3:01 ` Barry Song
2024-02-20 4:00 ` 李培锋
2024-02-20 7:16 ` Barry Song
2024-02-20 2:09 ` [PATCH 0/2] Support kshrinkd 李培锋
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=ZdQUmWxYuuP24w_1@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=gregkh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lipeifeng@oppo.com \
--cc=osalvador@suse.de \
--cc=tkjos@google.com \
--cc=v-songbaohua@oppo.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