From: Shakeel Butt <shakeel.butt@linux.dev>
To: Matthew Wilcox <willy@infradead.org>
Cc: Kairui Song <ryncsn@gmail.com>,
lsf-pc@lists.linux-foundation.org,
Axel Rasmussen <axelrasmussen@google.com>,
Yuanchu Xie <yuanchu@google.com>, Wei Xu <weixugc@google.com>,
linux-mm <linux-mm@kvack.org>
Subject: Re: [LSF/MM/BPF TOPIC] Improving MGLRU
Date: Fri, 27 Feb 2026 09:55:52 -0800 [thread overview]
Message-ID: <aaHaSRXNLJNLwvKh@linux.dev> (raw)
In-Reply-To: <aaBsrrmV25FTIkVX@casper.infradead.org>
On Thu, Feb 26, 2026 at 03:54:22PM +0000, Matthew Wilcox wrote:
> On Fri, Feb 20, 2026 at 01:25:33AM +0800, Kairui Song wrote:
> > MGLRU has been introduced in the mainline for years, but we still have two LRUs
> > today. There are many reasons MGLRU is still not the only LRU implementation in
> > the kernel.
>
> To my mind, the biggest problem with MGLRU is that Google dumped it on us
> and ran away. Commit 44958000bada claimed that it was now maintained and
> added three people as maintainers. In the six months since that commit,
> none of those three people have any commits in mm/! This is a shameful
> state of affairs.
>
> I say rip it out.
I have very similar concerns. Though rather than ripping it out, I would like
we put efforts in unifying the two reclaim mechanism (traditional & MGLRU) over
improving MGLRU.
>
next prev parent reply other threads:[~2026-02-27 17:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 17:25 Kairui Song
2026-02-20 18:24 ` Johannes Weiner
2026-02-21 6:03 ` Kairui Song
2026-02-26 1:55 ` Kalesh Singh
2026-02-26 3:06 ` Kairui Song
2026-02-26 10:10 ` wangzicheng
2026-02-26 15:54 ` Matthew Wilcox
2026-02-27 4:31 ` [LSF/MM/BPF] " Barry Song
2026-02-27 17:55 ` Shakeel Butt [this message]
2026-02-27 18:50 ` [LSF/MM/BPF TOPIC] " Gregory Price
2026-02-27 3:30 ` [LSF/MM/BPF] " Barry Song
2026-02-27 7:11 ` [LSF/MM/BPF TOPIC] " David Rientjes
2026-02-27 10:29 ` Vernon Yang
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=aaHaSRXNLJNLwvKh@linux.dev \
--to=shakeel.butt@linux.dev \
--cc=axelrasmussen@google.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=ryncsn@gmail.com \
--cc=weixugc@google.com \
--cc=willy@infradead.org \
--cc=yuanchu@google.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