linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: wangzicheng <wangzicheng@honor.com>
To: Kalesh Singh <kaleshsingh@google.com>
Cc: Suren Baghdasaryan <surenb@google.com>,
	"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>,
	yangxuzhe 00017436 <yangxuzhe@honor.com>,
	"T.J. Mercier" <tjmercier@google.com>,
	android-mm <android-mm@google.com>,
	"ryncsn@gmail.com" <ryncsn@gmail.com>
Subject: RE: [LSF/MM/BPF TOPIC] MGLRU on Android: Real-World Problems and Challenges
Date: Thu, 26 Feb 2026 13:06:11 +0000	[thread overview]
Message-ID: <586d56f766bf4181b99d6ba8106ebe0e@honor.com> (raw)
In-Reply-To: <CAC_TJveNB_beemBUdJ02tYpTj5c2Po6zQAMRzdFQD5WJKfTacQ@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.
> 
> Hi Zicheng,
> 
> I would be very interested in joining this discussion at LSF/MM as well.
> 
> I actually just replied to Kairui's MGLRU thread noting some similar
> observations we've made while evaluating MGLRU [1]. I think your
> findings in Q3 regarding high reclaim costs and tasks waiting in
> uninterruptible sleep corroborate the increased direct reclaim tail
> latencies we have been investigating on our end.
> 
> It will be valuable to discuss your large-scale field data and see how
> the workarounds you've implemented might inform the upstream
> discussions alongside Kairui's proposals.
> 
> [1]
> https://lore.kernel.org/all/CAC_TJvfi_5n2crGHbRVO0R8jdYcSCmgzUJPzhtSv
> WeCN6fCbQg@mail.gmail.com/#t
> 
> Thanks,
> Kalesh
> 
Hi Kalesh,

Thanks for following up and for sharing your observations.
For Q3, we have only tried some approaches so far and don’t have a solid solution yet.
We’d be happy to share our field data and some Perfetto traces. We believe it would 
be very helpful to discuss with you and Kairui at LSF/MM/BPF.

Best,
Zicheng

> > >
> > > 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-26 13:06 UTC|newest]

Thread overview: 10+ 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
2026-02-26  2:04     ` Kalesh Singh
2026-02-26 13:06       ` wangzicheng [this message]
2026-02-24 20:23 ` Barry Song
2026-02-25 10:43   ` wangzicheng
2026-02-26  8:03     ` Barry Song
2026-02-26 13:29       ` 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=586d56f766bf4181b99d6ba8106ebe0e@honor.com \
    --to=wangzicheng@honor.com \
    --cc=21cnbao@gmail.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=android-mm@google.com \
    --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=ryncsn@gmail.com \
    --cc=surenb@google.com \
    --cc=tao.wangtao@honor.com \
    --cc=tjmercier@google.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