All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory Price <gourry@gourry.net>
To: Shakeel Butt <shakeel.butt@linux.dev>
Cc: Matthew Wilcox <willy@infradead.org>,
	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 13:50:40 -0500	[thread overview]
Message-ID: <aaHngKLxfGp9wLG2@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <aaHaSRXNLJNLwvKh@linux.dev>

On Fri, Feb 27, 2026 at 09:55:52AM -0800, Shakeel Butt wrote:
> 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.
> 

I would agree.

If we could make the baseline MGLRU 2-generation and with behavioral
parity with the current LRU, then adding the additional generations
is just a mechanical change - and doesn't hurt anyone (default= 2 gen). 

But my understanding is MGLRU has behavior differences regarding its
preferences on how it ages anon vs file.

That mistake will cause significant pain in unifying them.

~Gregory


  reply	other threads:[~2026-02-27 18:50 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-19 17:25 [LSF/MM/BPF TOPIC] Improving MGLRU 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-03-02 17:46     ` Gregory Price
2026-03-05  6:27       ` Barry Song
2026-03-05  7:31         ` Gregory Price
2026-02-27 17:55   ` [LSF/MM/BPF TOPIC] " Shakeel Butt
2026-02-27 18:50     ` Gregory Price [this message]
2026-03-03  1:31     ` Axel Rasmussen
2026-03-03 13:39       ` Shakeel Butt
2026-03-05  6:46         ` Chen Ridong
2026-03-06 17:25       ` Nhat Pham
2026-03-03  1:30   ` Axel Rasmussen
2026-05-02  8:56   ` Hillf Danton
2026-05-02 11:53     ` Vlastimil Babka
2026-05-03  4:20       ` Hillf Danton
2026-02-27  3:30 ` [LSF/MM/BPF] " Barry Song
2026-03-02 11:10   ` Kairui Song
2026-03-03  4:06     ` Barry Song
2026-03-05 17:13       ` David Stevens
2026-03-05 23:40         ` Barry Song
2026-03-06 16:09           ` David Stevens
2026-02-27  7:11 ` [LSF/MM/BPF TOPIC] " David Rientjes
2026-02-27 10:29 ` Vernon Yang
2026-03-02 12:17   ` Kairui Song

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=aaHngKLxfGp9wLG2@gourry-fedora-PF4VCD3F \
    --to=gourry@gourry.net \
    --cc=axelrasmussen@google.com \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=ryncsn@gmail.com \
    --cc=shakeel.butt@linux.dev \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.