[PATCH 0/2] MAINTAINERS: MM updates (2)

[PATCH 0/2] MAINTAINERS: MM updates (2)

[David Hildenbrand (Arm)]

Hi,

some more MAINTAINERS updates with a focus on MGLRU and reclaim this
time.

Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
---
David Hildenbrand (Arm) (2):
      MAINTAINERS: MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU) update
      MAINTAINERS: remove myself from MEMORY MANAGEMENT - RECLAIM

 MAINTAINERS | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

---

base-commit: 7475ea8b58616b33c04afb976cf0fbaad9dd63fb

change-id: 20261107-maintainers_mglru-1e0a28d68060

--

Cheers,

David

[PATCH 1/2] MAINTAINERS: MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU) update

[David Hildenbrand (Arm)]

MGLRU is currently the only MM component without a dedicated component
maintainer. Fortunately, Kairui and Barry have been actively
contributing to MGLRU and have volunteered to take on more responsibility
by officially taking care of it.

Given that Kairui is already an established MM component maintainer in
a related MM component (SWAP), add him as an MGLRU maintainer right away.

For Barry, the idea is to transition him towards a component maintainer
role over the coming months, starting by moving him to the top of the
reviewer list.

Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
---
 MAINTAINERS | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 222b7fc2c3aa..e7ac319a570c 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -17635,10 +17635,10 @@ K:	(?i:vmemmap)
 
 MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU)
 M:	Andrew Morton <akpm@linux-foundation.org>
-R:	Kairui Song <kasong@tencent.com>
+M:	Kairui Song <kasong@tencent.com>
+R:	Barry Song <baohua@kernel.org>
 R:	Qi Zheng <qi.zheng@linux.dev>
 R:	Shakeel Butt <shakeel.butt@linux.dev>
-R:	Barry Song <baohua@kernel.org>
 R:	Axel Rasmussen <axelrasmussen@google.com>
 R:	Yuanchu Xie <yuanchu@google.com>
 R:	Wei Xu <weixugc@google.com>

-- 
2.43.0

[PATCH 2/2] MAINTAINERS: remove myself from MEMORY MANAGEMENT - RECLAIM

[David Hildenbrand (Arm)]

I don't really get to look at most reclaim related stuff. For things
that are actually relevant for me, I'm sure people will CC me.

So remove myself from the MEMORY MANAGEMENT - RECLAIM section for now
to have a bit less noise in my inbox.

Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
---
 MAINTAINERS | 1 -
 1 file changed, 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index e7ac319a570c..7dc8548236b9 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -17808,7 +17808,6 @@ F:	tools/mm/page_owner_sort.c
 MEMORY MANAGEMENT - RECLAIM
 M:	Andrew Morton <akpm@linux-foundation.org>
 M:	Johannes Weiner <hannes@cmpxchg.org>
-R:	David Hildenbrand <david@kernel.org>
 R:	Michal Hocko <mhocko@kernel.org>
 R:	Qi Zheng <qi.zheng@linux.dev>
 R:	Shakeel Butt <shakeel.butt@linux.dev>

-- 
2.43.0

Re: [PATCH 1/2] MAINTAINERS: MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU) update

[Andrew Morton]

On Mon, 09 Nov 2026 19:31:53 +0100 "David Hildenbrand (Arm)" <david@kernel.org> wrote:

> MGLRU is currently the only MM component without a dedicated component
> maintainer. Fortunately, Kairui and Barry have been actively
> contributing to MGLRU and have volunteered to take on more responsibility
> by officially taking care of it.
> 
> Given that Kairui is already an established MM component maintainer in
> a related MM component (SWAP), add him as an MGLRU maintainer right away.
> 
> For Barry, the idea is to transition him towards a component maintainer
> role over the coming months, starting by moving him to the top of the
> reviewer list.
> 

Yay, thanks guys.  It's been wonderful to see the rebirth of MGLRU over
the past ~year.

When do we get to remove the legacy LRU???

> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -17635,10 +17635,10 @@ K:	(?i:vmemmap)
>  
>  MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU)
>  M:	Andrew Morton <akpm@linux-foundation.org>
> -R:	Kairui Song <kasong@tencent.com>
> +M:	Kairui Song <kasong@tencent.com>
> +R:	Barry Song <baohua@kernel.org>

Totally-Acked-by:me.

Re: [PATCH 1/2] MAINTAINERS: MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU) update

[SJ Park]

On Mon, 09 Nov 2026 19:31:53 +0100 "David Hildenbrand (Arm)" <david@kernel.org> wrote:

> MGLRU is currently the only MM component without a dedicated component
> maintainer. Fortunately, Kairui and Barry have been actively
> contributing to MGLRU and have volunteered to take on more responsibility
> by officially taking care of it.
> 
> Given that Kairui is already an established MM component maintainer in
> a related MM component (SWAP), add him as an MGLRU maintainer right away.
> 
> For Barry, the idea is to transition him towards a component maintainer
> role over the coming months, starting by moving him to the top of the
> reviewer list.

Congrats and thanks for stepping up, Kairui and Barry!

> 
> Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>

Acked-by: SJ Park <sj@kernel.org>


Thanks,
SJ

[...]

Re: [PATCH 2/2] MAINTAINERS: remove myself from MEMORY MANAGEMENT - RECLAIM

[SJ Park]

On Mon, 09 Nov 2026 19:31:54 +0100 "David Hildenbrand (Arm)" <david@kernel.org> wrote:

> I don't really get to look at most reclaim related stuff. For things
> that are actually relevant for me, I'm sure people will CC me.
> 
> So remove myself from the MEMORY MANAGEMENT - RECLAIM section for now
> to have a bit less noise in my inbox.
> 
> Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>

Acked-by: SJ Park <sj@kernel.org>


Thanks,
SJ

[...]

Re: [PATCH 1/2] MAINTAINERS: MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU) update

[Qi Zheng]

On 11/10/26 2:31 AM, David Hildenbrand (Arm) wrote:
> MGLRU is currently the only MM component without a dedicated component
> maintainer. Fortunately, Kairui and Barry have been actively
> contributing to MGLRU and have volunteered to take on more responsibility
> by officially taking care of it.
> 
> Given that Kairui is already an established MM component maintainer in
> a related MM component (SWAP), add him as an MGLRU maintainer right away.
> 
> For Barry, the idea is to transition him towards a component maintainer
> role over the coming months, starting by moving him to the top of the
> reviewer list.
> 
> Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
> ---
>   MAINTAINERS | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)

Acked-by: Qi Zheng <qi.zheng@linux.dev>

> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 222b7fc2c3aa..e7ac319a570c 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -17635,10 +17635,10 @@ K:	(?i:vmemmap)
>   
>   MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU)
>   M:	Andrew Morton <akpm@linux-foundation.org>
> -R:	Kairui Song <kasong@tencent.com>
> +M:	Kairui Song <kasong@tencent.com>
> +R:	Barry Song <baohua@kernel.org>
>   R:	Qi Zheng <qi.zheng@linux.dev>
>   R:	Shakeel Butt <shakeel.butt@linux.dev>
> -R:	Barry Song <baohua@kernel.org>
>   R:	Axel Rasmussen <axelrasmussen@google.com>
>   R:	Yuanchu Xie <yuanchu@google.com>
>   R:	Wei Xu <weixugc@google.com>
> 

Re: [PATCH 1/2] MAINTAINERS: MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU) update

[Baoquan He]

On 11/09/26 at 07:31pm, David Hildenbrand (Arm) wrote:
> MGLRU is currently the only MM component without a dedicated component
> maintainer. Fortunately, Kairui and Barry have been actively
> contributing to MGLRU and have volunteered to take on more responsibility
> by officially taking care of it.
> 
> Given that Kairui is already an established MM component maintainer in
> a related MM component (SWAP), add him as an MGLRU maintainer right away.
> 
> For Barry, the idea is to transition him towards a component maintainer
> role over the coming months, starting by moving him to the top of the
> reviewer list.
> 
> Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
> ---
>  MAINTAINERS | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

Well deserved, congrats to both.

Reviewed-by: Baoquan He <baoquan.he@linux.dev>

> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 222b7fc2c3aa..e7ac319a570c 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -17635,10 +17635,10 @@ K:	(?i:vmemmap)
>  
>  MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU)
>  M:	Andrew Morton <akpm@linux-foundation.org>
> -R:	Kairui Song <kasong@tencent.com>
> +M:	Kairui Song <kasong@tencent.com>
> +R:	Barry Song <baohua@kernel.org>
>  R:	Qi Zheng <qi.zheng@linux.dev>
>  R:	Shakeel Butt <shakeel.butt@linux.dev>
> -R:	Barry Song <baohua@kernel.org>
>  R:	Axel Rasmussen <axelrasmussen@google.com>
>  R:	Yuanchu Xie <yuanchu@google.com>
>  R:	Wei Xu <weixugc@google.com>
> 
> -- 
> 2.43.0
> 

Re: [PATCH 1/2] MAINTAINERS: MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU) update

[Muchun Song]

> On Nov 10, 2026, at 02:31, David Hildenbrand (Arm) <david@kernel.org> wrote:
> 
> MGLRU is currently the only MM component without a dedicated component
> maintainer. Fortunately, Kairui and Barry have been actively
> contributing to MGLRU and have volunteered to take on more responsibility
> by officially taking care of it.
> 
> Given that Kairui is already an established MM component maintainer in
> a related MM component (SWAP), add him as an MGLRU maintainer right away.
> 
> For Barry, the idea is to transition him towards a component maintainer
> role over the coming months, starting by moving him to the top of the
> reviewer list.
> 
> Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>

Acked-by: Muchun Song <muchun.song@linux.dev>

Thanks.

Re: [PATCH 2/2] MAINTAINERS: remove myself from MEMORY MANAGEMENT - RECLAIM

[Muchun Song]

> On Nov 10, 2026, at 02:31, David Hildenbrand (Arm) <david@kernel.org> wrote:
> 
> I don't really get to look at most reclaim related stuff. For things
> that are actually relevant for me, I'm sure people will CC me.
> 
> So remove myself from the MEMORY MANAGEMENT - RECLAIM section for now
> to have a bit less noise in my inbox.
> 
> Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>

Acked-by: Muchun Song <muchun.song@linux.dev>

Thanks.

Re: [PATCH 1/2] MAINTAINERS: MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU) update

[Baolin Wang]

On 11/10/26 2:31 AM, David Hildenbrand (Arm) wrote:
> MGLRU is currently the only MM component without a dedicated component
> maintainer. Fortunately, Kairui and Barry have been actively
> contributing to MGLRU and have volunteered to take on more responsibility
> by officially taking care of it.
> 
> Given that Kairui is already an established MM component maintainer in
> a related MM component (SWAP), add him as an MGLRU maintainer right away.
> 
> For Barry, the idea is to transition him towards a component maintainer
> role over the coming months, starting by moving him to the top of the
> reviewer list.
> 
> Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
> ---

Thanks for your great work, Kairui and Barry.
Acked-by: Baolin Wang <baolin.wang@linux.alibaba.com>

Re: [PATCH 2/2] MAINTAINERS: remove myself from MEMORY MANAGEMENT - RECLAIM

[Baolin Wang]

On 11/10/26 2:31 AM, David Hildenbrand (Arm) wrote:
> I don't really get to look at most reclaim related stuff. For things
> that are actually relevant for me, I'm sure people will CC me.
> 
> So remove myself from the MEMORY MANAGEMENT - RECLAIM section for now
> to have a bit less noise in my inbox.
> 
> Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
> ---

Acked-by: Baolin Wang <baolin.wang@linux.alibaba.com>

Re: [PATCH 1/2] MAINTAINERS: MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU) update

[Lance Yang]

On Mon, Nov 09, 2026 at 07:31:53PM +0100, David Hildenbrand (Arm) wrote:
>MGLRU is currently the only MM component without a dedicated component
>maintainer. Fortunately, Kairui and Barry have been actively
>contributing to MGLRU and have volunteered to take on more responsibility
>by officially taking care of it.
>
>Given that Kairui is already an established MM component maintainer in
>a related MM component (SWAP), add him as an MGLRU maintainer right away.
>
>For Barry, the idea is to transition him towards a component maintainer
>role over the coming months, starting by moving him to the top of the
>reviewer list.
>
>Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
>---

Reviewed-by: Lance Yang <lance.yang@linux.dev>

Re: [PATCH 1/2] MAINTAINERS: MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU) update

[Ridong Chen]

On 11/10/2026 2:31 AM, David Hildenbrand (Arm) wrote:
> MGLRU is currently the only MM component without a dedicated component
> maintainer. Fortunately, Kairui and Barry have been actively
> contributing to MGLRU and have volunteered to take on more responsibility
> by officially taking care of it.
> 
> Given that Kairui is already an established MM component maintainer in
> a related MM component (SWAP), add him as an MGLRU maintainer right away.
> 
> For Barry, the idea is to transition him towards a component maintainer
> role over the coming months, starting by moving him to the top of the
> reviewer list.
> 
> Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
> ---
>   MAINTAINERS | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 222b7fc2c3aa..e7ac319a570c 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -17635,10 +17635,10 @@ K:	(?i:vmemmap)
>   
>   MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU)
>   M:	Andrew Morton <akpm@linux-foundation.org>
> -R:	Kairui Song <kasong@tencent.com>
> +M:	Kairui Song <kasong@tencent.com>
> +R:	Barry Song <baohua@kernel.org>
>   R:	Qi Zheng <qi.zheng@linux.dev>
>   R:	Shakeel Butt <shakeel.butt@linux.dev>
> -R:	Barry Song <baohua@kernel.org>
>   R:	Axel Rasmussen <axelrasmussen@google.com>
>   R:	Yuanchu Xie <yuanchu@google.com>
>   R:	Wei Xu <weixugc@google.com>
> 

Reviewed-by: Ridong Chen <ridong.chen@linux.dev>
Thanks.

-- 
Best regards
Ridong

Re: [PATCH 1/2] MAINTAINERS: MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU) update

[Kairui Song]

On Tue, Nov 10, 2026 at 2:46 AM David Hildenbrand (Arm)
<david@kernel.org> wrote:
>
> MGLRU is currently the only MM component without a dedicated component
> maintainer. Fortunately, Kairui and Barry have been actively
> contributing to MGLRU and have volunteered to take on more responsibility
> by officially taking care of it.
>
> Given that Kairui is already an established MM component maintainer in
> a related MM component (SWAP), add him as an MGLRU maintainer right away.
>
> For Barry, the idea is to transition him towards a component maintainer
> role over the coming months, starting by moving him to the top of the
> reviewer list.
>
> Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
> ---
>  MAINTAINERS | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 222b7fc2c3aa..e7ac319a570c 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -17635,10 +17635,10 @@ K:    (?i:vmemmap)
>
>  MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU)
>  M:     Andrew Morton <akpm@linux-foundation.org>
> -R:     Kairui Song <kasong@tencent.com>
> +M:     Kairui Song <kasong@tencent.com>
> +R:     Barry Song <baohua@kernel.org>
>  R:     Qi Zheng <qi.zheng@linux.dev>
>  R:     Shakeel Butt <shakeel.butt@linux.dev>
> -R:     Barry Song <baohua@kernel.org>
>  R:     Axel Rasmussen <axelrasmussen@google.com>
>  R:     Yuanchu Xie <yuanchu@google.com>
>  R:     Wei Xu <weixugc@google.com>
>
> --
> 2.43.0

Thanks for the trust. Looking forward to pushing MGLRU's development
even further with Barry!

Acked-by: Kairui Song <kasong@tencent.com>

Re: [PATCH 1/2] MAINTAINERS: MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU) update

[Barry Song]

On Tue, Nov 10, 2026 at 2:32 AM David Hildenbrand (Arm)
<david@kernel.org> wrote:
>
> MGLRU is currently the only MM component without a dedicated component
> maintainer. Fortunately, Kairui and Barry have been actively
> contributing to MGLRU and have volunteered to take on more responsibility
> by officially taking care of it.
>
> Given that Kairui is already an established MM component maintainer in
> a related MM component (SWAP), add him as an MGLRU maintainer right away.
>
> For Barry, the idea is to transition him towards a component maintainer
> role over the coming months, starting by moving him to the top of the
> reviewer list.
>
> Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
> ---

Thanks very much to David for all his work on this.

I also want to thank Andrew, SJ, Qi, Baoquan, Muchun,
Baolin, Lance, Ridong, and Kairui for their encouragement
and kind words.

Acked-by: Barry Song <baohua@kernel.org>

Thanks,
Barry

Re: [PATCH 1/2] MAINTAINERS: MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU) update

[Lorenzo Stoakes (ARM)]

On Mon, Nov 09, 2026 at 07:31:53PM +0100, David Hildenbrand (Arm) wrote:
> MGLRU is currently the only MM component without a dedicated component
> maintainer. Fortunately, Kairui and Barry have been actively
> contributing to MGLRU and have volunteered to take on more responsibility
> by officially taking care of it.
>
> Given that Kairui is already an established MM component maintainer in
> a related MM component (SWAP), add him as an MGLRU maintainer right away.
>
> For Barry, the idea is to transition him towards a component maintainer
> role over the coming months, starting by moving him to the top of the
> reviewer list.
>
> Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>

Acked-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>

Congrats Kairui and Barry! :)

I am so glad to see the proactive efforts people have made to get MGLRU moving
forwards again, it's a real success story in mm.

Thanks to everybody for their efforts in making this happen! :)

> ---
>  MAINTAINERS | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 222b7fc2c3aa..e7ac319a570c 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -17635,10 +17635,10 @@ K:	(?i:vmemmap)
>
>  MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU)
>  M:	Andrew Morton <akpm@linux-foundation.org>
> -R:	Kairui Song <kasong@tencent.com>
> +M:	Kairui Song <kasong@tencent.com>
> +R:	Barry Song <baohua@kernel.org>
>  R:	Qi Zheng <qi.zheng@linux.dev>
>  R:	Shakeel Butt <shakeel.butt@linux.dev>
> -R:	Barry Song <baohua@kernel.org>
>  R:	Axel Rasmussen <axelrasmussen@google.com>
>  R:	Yuanchu Xie <yuanchu@google.com>
>  R:	Wei Xu <weixugc@google.com>
>
> --
> 2.43.0
>

--
Cheers, Lorenzo

Re: [PATCH 2/2] MAINTAINERS: remove myself from MEMORY MANAGEMENT - RECLAIM

[Lorenzo Stoakes (ARM)]

On Mon, Nov 09, 2026 at 07:31:54PM +0100, David Hildenbrand (Arm) wrote:
> I don't really get to look at most reclaim related stuff. For things
> that are actually relevant for me, I'm sure people will CC me.
>
> So remove myself from the MEMORY MANAGEMENT - RECLAIM section for now
> to have a bit less noise in my inbox.
>
> Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>

Understandable! The ML is crazy of late.

And... Hmm... maybe time for me to pare down some of my R:'s too :)

Acked-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>

> ---
>  MAINTAINERS | 1 -
>  1 file changed, 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index e7ac319a570c..7dc8548236b9 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -17808,7 +17808,6 @@ F:	tools/mm/page_owner_sort.c
>  MEMORY MANAGEMENT - RECLAIM
>  M:	Andrew Morton <akpm@linux-foundation.org>
>  M:	Johannes Weiner <hannes@cmpxchg.org>
> -R:	David Hildenbrand <david@kernel.org>
>  R:	Michal Hocko <mhocko@kernel.org>
>  R:	Qi Zheng <qi.zheng@linux.dev>
>  R:	Shakeel Butt <shakeel.butt@linux.dev>
>
> --
> 2.43.0
>

--
Cheers, Lorenzo

Re: [PATCH 1/2] MAINTAINERS: MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU) update

[Kairui Song]

On Tue, Nov 10, 2026 at 2:55 AM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Mon, 09 Nov 2026 19:31:53 +0100 "David Hildenbrand (Arm)" <david@kernel.org> wrote:
>
> > MGLRU is currently the only MM component without a dedicated component
> > maintainer. Fortunately, Kairui and Barry have been actively
> > contributing to MGLRU and have volunteered to take on more responsibility
> > by officially taking care of it.
> >
> > Given that Kairui is already an established MM component maintainer in
> > a related MM component (SWAP), add him as an MGLRU maintainer right away.
> >
> > For Barry, the idea is to transition him towards a component maintainer
> > role over the coming months, starting by moving him to the top of the
> > reviewer list.
> >
>
> Yay, thanks guys.  It's been wonderful to see the rebirth of MGLRU over
> the past ~year.
>
> When do we get to remove the legacy LRU???

That's on my radar :), though it will take some time and it's always
hard to give an exact timeline...

Items I'm aware of to sort out besides the FG series, maybe we can try
to make MGLRU the default at some point during this process:
- Refault distance, otherwise we still have a major regression in
heavily overcommitted cases, also protects cross-memcg workingset
thrashing. I also have an idea to remove memcg id and node id field
from the shadow so it will have enough space to hold both the gen
number and distance, will post that in a few weeks hopefully.
- Memcg LRU vs. iterator (Ridong once tried to unify that, and it's
good to see there have been optimizations for memcg LRU itself
recently from Max).
  I also noticed recently that the Memcg's LRU reclaim balance is
somehow a bit broken, I'm not exactly sure why, nor a very major
problem, I will look into it later.
- Isolation protection (from Hui, not a very high priority, but still
on the list, we don't want premature OOM).
- IO cost & swappiness (Barry and I are still looking into this, with
an series posted).
- Page flags usage issue (FG cuts it down by 1, though it's still tight).

We also have aging optimizations and async aging planned. I'm not sure
if we are missing anything else, but we are getting close and with a
sane todo list.

> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -17635,10 +17635,10 @@ K:  (?i:vmemmap)
> >
> >  MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU)
> >  M:   Andrew Morton <akpm@linux-foundation.org>
> > -R:   Kairui Song <kasong@tencent.com>
> > +M:   Kairui Song <kasong@tencent.com>
> > +R:   Barry Song <baohua@kernel.org>
>
> Totally-Acked-by:me.

Thanks!

Re: [PATCH 1/2] MAINTAINERS: MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU) update

[Barry Song]

On Tue, Nov 10, 2026 at 5:53 PM Lorenzo Stoakes (ARM) <ljs@kernel.org> wrote:
>
> On Mon, Nov 09, 2026 at 07:31:53PM +0100, David Hildenbrand (Arm) wrote:
> > MGLRU is currently the only MM component without a dedicated component
> > maintainer. Fortunately, Kairui and Barry have been actively
> > contributing to MGLRU and have volunteered to take on more responsibility
> > by officially taking care of it.
> >
> > Given that Kairui is already an established MM component maintainer in
> > a related MM component (SWAP), add him as an MGLRU maintainer right away.
> >
> > For Barry, the idea is to transition him towards a component maintainer
> > role over the coming months, starting by moving him to the top of the
> > reviewer list.
> >
> > Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
>
> Acked-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
>
> Congrats Kairui and Barry! :)
>
> I am so glad to see the proactive efforts people have made to get MGLRU moving
> forwards again, it's a real success story in mm.
>
> Thanks to everybody for their efforts in making this happen! :)

Thanks very much for your kind words, Lorenzo!

Given your earlier involvement with MGLRU, it's great
to see it continuing to move forward!

Thanks,
Barry

Re: [PATCH 1/2] MAINTAINERS: MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU) update

[Lian Wang]

On Mon, Nov 9, 2026 at 07:31:53PM +0100, David Hildenbrand wrote:
> Fortunately, Kairui and Barry have been actively
> contributing to MGLRU and have volunteered to take on more responsibility
> by officially taking care of it.

Congratulations, Kairui and Barry! Thank you both for all the work
you've put into MGLRU and for everything I've learned from you. I'm
grateful to have you both as friends and mentors.

I look forward to following your lead and contributing alongside you.

Reviewed-by: Lian Wang <lianux.mm@gmail.com>

Best,
Lian

Re: [PATCH 1/2] MAINTAINERS: MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU) update

[Barry Song]

On Wed, Nov 11, 2026 at 2:16 PM Kairui Song <ryncsn@gmail.com> wrote:
>
> On Tue, Nov 10, 2026 at 2:55 AM Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > On Mon, 09 Nov 2026 19:31:53 +0100 "David Hildenbrand (Arm)" <david@kernel.org> wrote:
> >
> > > MGLRU is currently the only MM component without a dedicated component
> > > maintainer. Fortunately, Kairui and Barry have been actively
> > > contributing to MGLRU and have volunteered to take on more responsibility
> > > by officially taking care of it.
> > >
> > > Given that Kairui is already an established MM component maintainer in
> > > a related MM component (SWAP), add him as an MGLRU maintainer right away.
> > >
> > > For Barry, the idea is to transition him towards a component maintainer
> > > role over the coming months, starting by moving him to the top of the
> > > reviewer list.
> > >
> >
> > Yay, thanks guys.  It's been wonderful to see the rebirth of MGLRU over
> > the past ~year.
> >
> > When do we get to remove the legacy LRU???
>
> That's on my radar :), though it will take some time and it's always
> hard to give an exact timeline...
>
> Items I'm aware of to sort out besides the FG series, maybe we can try
> to make MGLRU the default at some point during this process:
> - Refault distance, otherwise we still have a major regression in
> heavily overcommitted cases, also protects cross-memcg workingset
> thrashing. I also have an idea to remove memcg id and node id field
> from the shadow so it will have enough space to hold both the gen
> number and distance, will post that in a few weeks hopefully.
> - Memcg LRU vs. iterator (Ridong once tried to unify that, and it's
> good to see there have been optimizations for memcg LRU itself
> recently from Max).
>   I also noticed recently that the Memcg's LRU reclaim balance is
> somehow a bit broken, I'm not exactly sure why, nor a very major
> problem, I will look into it later.
> - Isolation protection (from Hui, not a very high priority, but still
> on the list, we don't want premature OOM).
> - IO cost & swappiness (Barry and I are still looking into this, with
> an series posted).
> - Page flags usage issue (FG cuts it down by 1, though it's still tight).
>
> We also have aging optimizations and async aging planned. I'm not sure
> if we are missing anything else, but we are getting close and with a
> sane todo list.

Thanks very much, Kairui. Besides the items above, I am also
thinking about a few more:

- Cross-memcg aging / look-around folio promotion (folios with
large mapcounts across multiple memcgs still easily fall back to
rmap walks today)
- mmap_lock contention during aging (perhaps switching to VMA
locks, as mmap_lock contention can cause jank in Android
foreground UI)
- Baoquan's PUD filter
- Making MGLRU more friendly to Android foreground/background
workloads

Thanks,
Barry