linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: wangzicheng <wangzicheng@honor.com>
To: Suren Baghdasaryan <surenb@google.com>
Cc: "lsf-pc@lists.linux-foundation.org"
	<lsf-pc@lists.linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	wangxin 00023513 <wangxin23@honor.com>, gao xu <gaoxu2@honor.com>,
	wangtao <tao.wangtao@honor.com>,
	liulu 00013167 <liulu.liu@honor.com>,
	zhouxiaolong <zhouxiaolong9@honor.com>,
	linkunli <linkunli@honor.com>,
	"kasong@tencent.com" <kasong@tencent.com>,
	"21cnbao@gmail.com" <21cnbao@gmail.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"axelrasmussen@google.com" <axelrasmussen@google.com>,
	"yuanchu@google.com" <yuanchu@google.com>,
	"weixugc@google.com" <weixugc@google.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	"Liam.Howlett@oracle.com" <Liam.Howlett@oracle.com>,
	"willy@infradead.org" <willy@infradead.org>,
	Kalesh Singh <kaleshsingh@google.com>,
	yangxuzhe 00017436 <yangxuzhe@honor.com>
Subject: RE: [LSF/MM/BPF TOPIC] MGLRU on Android: Real-World Problems and Challenges
Date: Wed, 25 Feb 2026 10:46:47 +0000	[thread overview]
Message-ID: <e3734e2cfac3403da02213b64af8c5b4@honor.com> (raw)
In-Reply-To: <CAJuCfpHzTdwcGh8wXetEcAy-93-WqPmoyDnbC8UhzGttpcm_Cw@mail.gmail.com>

> >
> > We are happy to share more detailed data and experiments and to help
> > with PoCs and large-scale validation if there is interest in
> > pursuing these directions.
> 
> For obvious reasons I'm interested in this discussion. We also notice
> some shortcomings of MGLRU and would like to collaborate on resolving
> them.
> Thanks,
> Suren.
> 
Hi Suren,

thanks, we’d be very happy to work together on this.

> >
> > Reference
> > [1] https://lore.kernel.org/linux-mm/20251128025315.3520689-1-
> wangzicheng@honor.com/
> > [2] https://android-
> review.googlesource.com/c/kernel/common/+/3866554
> > [3] https://android-
> review.googlesource.com/c/kernel/common/+/3870920
> > [4] https://lwn.net/Articles/1051882/
> >
> > --
> > Best regards, and wishing you a prosperous Year of the Horse,
> > Zicheng Wang

  reply	other threads:[~2026-02-25 10:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-24  3:17 wangzicheng
2026-02-24 17:10 ` Suren Baghdasaryan
2026-02-25 10:46   ` wangzicheng [this message]
2026-02-24 20:23 ` Barry Song
2026-02-25 10:43   ` wangzicheng
  -- strict thread matches above, loose matches on Subject: below --
2026-02-14 10:06 wangzicheng

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=e3734e2cfac3403da02213b64af8c5b4@honor.com \
    --to=wangzicheng@honor.com \
    --cc=21cnbao@gmail.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=axelrasmussen@google.com \
    --cc=gaoxu2@honor.com \
    --cc=kaleshsingh@google.com \
    --cc=kasong@tencent.com \
    --cc=linkunli@honor.com \
    --cc=linux-mm@kvack.org \
    --cc=liulu.liu@honor.com \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=rdunlap@infradead.org \
    --cc=surenb@google.com \
    --cc=tao.wangtao@honor.com \
    --cc=wangxin23@honor.com \
    --cc=weixugc@google.com \
    --cc=willy@infradead.org \
    --cc=yangxuzhe@honor.com \
    --cc=yuanchu@google.com \
    --cc=zhouxiaolong9@honor.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