From: Kairui Song <ryncsn@gmail.com>
To: Vernon Yang <vernon2gm@gmail.com>
Cc: 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: Mon, 2 Mar 2026 20:17:16 +0800 [thread overview]
Message-ID: <CAMgjq7Aofz8qf4x4Pd7rQgSmL1exT86-wxb3L9zZWdbQgvhW1A@mail.gmail.com> (raw)
In-Reply-To: <f4c9b715-be7a-4587-90fa-97f6b72938eb@gmail.com>
On Fri, Feb 27, 2026 at 6:29 PM Vernon Yang <vernon2gm@gmail.com> wrote:
> Hi Kairui,
>
> I would be very interested in discussing this topic as well.
>
> In Linux desktop distributions, when the system rapidly enters low
> memory state, it is almost impossible to enter S4, the success rate
> only is 10%. When analyzing this issue, it was identified as the
> inability to reclaim memory. Further investigation revealed that:
Hi Vernon,
Thanks for the comment!
> If we could directly remove the force protection of the youngest two
> generations, this issue would also be resolved, and the solution would
> be more universally applicable.
Yeah, that's also what I have in mind. Such issues should be fixable
if we find a way to remove or optimize gen protection.
prev parent reply other threads:[~2026-03-02 12:17 UTC|newest]
Thread overview: 15+ 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 ` [LSF/MM/BPF TOPIC] " Shakeel Butt
2026-02-27 18:50 ` Gregory Price
2026-02-27 3:30 ` [LSF/MM/BPF] " Barry Song
2026-03-02 11:10 ` Kairui Song
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 [this message]
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=CAMgjq7Aofz8qf4x4Pd7rQgSmL1exT86-wxb3L9zZWdbQgvhW1A@mail.gmail.com \
--to=ryncsn@gmail.com \
--cc=axelrasmussen@google.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=vernon2gm@gmail.com \
--cc=weixugc@google.com \
--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