From: Vlastimil Babka <vbabka@suse.com>
To: Hillf Danton <hdanton@sina.com>, Matthew Wilcox <willy@infradead.org>
Cc: Kairui Song <ryncsn@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [LSF/MM/BPF TOPIC] Improving MGLRU
Date: Sat, 2 May 2026 13:53:20 +0200 [thread overview]
Message-ID: <83c146d2-d52f-41f3-975d-ad607a6f741c@suse.com> (raw)
In-Reply-To: <20260502085645.262-1-hdanton@sina.com>
On 5/2/26 10:56, Hillf Danton wrote:
> On Thu, 26 Feb 2026 15:54:22 +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 suspect you are kidding again. Go and cut it off then we know how sharp
> you are.
>
I can't wait for the day when you finally decide to do that with your e-mail
"contributions".
next prev parent reply other threads:[~2026-05-02 11:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMgjq7BoekNjg-Ra3C8M7=8=75su38w=HD782T5E_cxyeCeH_g@mail.gmail.com>
[not found] ` <aaBsrrmV25FTIkVX@casper.infradead.org>
2026-05-02 8:56 ` [LSF/MM/BPF TOPIC] Improving MGLRU Hillf Danton
2026-05-02 11:53 ` Vlastimil Babka [this message]
2026-05-03 4:20 ` Hillf Danton
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=83c146d2-d52f-41f3-975d-ad607a6f741c@suse.com \
--to=vbabka@suse.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryncsn@gmail.com \
--cc=willy@infradead.org \
/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