Skip to contentSkip to conversation

MAINTAINERS: mark MGLRU as maintained

PATCH Applied Axel Rasmussen 3 participants 5 messages Aug 15, 2025 – Aug 16, 2025 Memory management

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 MAINTAINERS: mark MGLRU as maintained

The three folks being added here are actively working on MGLRU within Google, so we can review patches for this feature and plan to contribute some improvements / extensions to it on an ongoing basis.

With three of us we may have some hope filling Yu Zhao's shoes, since he has moved on to other projects these days.

---
 MAINTAINERS | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
MAINTAINERS +17 -0
index daf520a13bdf..8e987f2668cd 100644
@@ -16058,6 +16058,23 @@ F:	mm/mempolicy.c
 F:	mm/migrate.c
 F:	mm/migrate_device.c
 
+MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU)
+M:	Andrew Morton <[email protected]>
+M:	Axel Rasmussen <[email protected]>
+M:	Yuanchu Xie <[email protected]>
+R:	Wei Xu <[email protected]>
+L:	[email protected]
+S:	Maintained
+W:	http://www.linux-mm.org
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
+F:	Documentation/admin-guide/mm/multigen_lru.rst
+F:	Documentation/mm/multigen_lru.rst
+F:	include/linux/mm_inline.h
+F:	include/linux/mmzone.h
+F:	mm/swap.c
+F:	mm/vmscan.c
+F:	mm/workingset.c
+
 MEMORY MANAGEMENT - MISC
 M:	Andrew Morton <[email protected]>
 M:	David Hildenbrand <[email protected]>
Signature · 1 line
2.51.0.rc1.163.g2494970778-goog
#1 lore raw
Quoted 17 lines · Axel Rasmussen

The three folks being added here are actively working on MGLRU within Google, so we can review patches for this feature and plan to contribute some improvements / extensions to it on an ongoing basis.

With three of us we may have some hope filling Yu Zhao's shoes, since he has moved on to other projects these days.

---
 MAINTAINERS | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
MAINTAINERS +0 -0
index daf520a13bdf..8e987f2668cd 100644

MAINTAINERS F: mm/mempolicy.c · line 16061

Quoted 4 lines
MAINTAINERS +1 -0
@@ -16058,6 +16058,23 @@ F:	mm/mempolicy.c
 F:	mm/migrate.c
 F:	mm/migrate_device.c
 
+MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU)

Why not just add yourselves (and the missing files) to the existing reclaim section? Eventually we want a single reclaim solution, so why not start with single reviewer section?

Quoted 22 lines
MAINTAINERS +16 -0
+M:	Andrew Morton <[email protected]>
+M:	Axel Rasmussen <[email protected]>
+M:	Yuanchu Xie <[email protected]>
+R:	Wei Xu <[email protected]>
+L:	[email protected]
+S:	Maintained
+W:	http://www.linux-mm.org
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
+F:	Documentation/admin-guide/mm/multigen_lru.rst
+F:	Documentation/mm/multigen_lru.rst
+F:	include/linux/mm_inline.h
+F:	include/linux/mmzone.h
+F:	mm/swap.c
+F:	mm/vmscan.c
+F:	mm/workingset.c
+
 MEMORY MANAGEMENT - MISC
 M:	Andrew Morton <[email protected]>
 M:	David Hildenbrand <[email protected]>
Signature · 1 line
2.51.0.rc1.163.g2494970778-goog
#2 lore raw
Quoted 22 lines · Shakeel Butt
Quoted 20 lines · Axel Rasmussen

The three folks being added here are actively working on MGLRU within Google, so we can review patches for this feature and plan to contribute some improvements / extensions to it on an ongoing basis.

With three of us we may have some hope filling Yu Zhao's shoes, since he has moved on to other projects these days.

---
 MAINTAINERS | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
MAINTAINERS +0 -0
index daf520a13bdf..8e987f2668cd 100644
@@ -16058,6 +16058,23 @@ F:   mm/mempolicy.c
 F:   mm/migrate.c
 F:   mm/migrate_device.c
 
Quoted 5 lines

MAINTAINERS F: mm/mempolicy.c · line 16061

Quoted 1 line
MAINTAINERS +1 -0
+MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU)

Why not just add yourselves (and the missing files) to the existing reclaim section? Eventually we want a single reclaim solution, so why not start with single reviewer section?

Sure, I can see the argument for that.

I suppose the case against would be, perhaps the folks already listed in the RECLAIM section don't want to additionally get e-mail for the extra files listed in this patch? (Perhaps mostly the MGLRU documentation, the rest of them aren't necessarily MGLRU specific.)

I don't have a strong preference either way, I think mostly I'd be interested to know Andrew's or the other reviewers' preference. Note Lorenzo suggested a separate MGLRU section here:
https://lkml.org/lkml/2025/8/14/271

Quoted 23 lines
Quoted 23 lines
MAINTAINERS +16 -1
+M:   Andrew Morton <[email protected]>
+M:   Axel Rasmussen <[email protected]>
+M:   Yuanchu Xie <[email protected]>
+R:   Wei Xu <[email protected]>
+L:   [email protected]
+S:   Maintained
+W:   http://www.linux-mm.org
+T:   git git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
+F:   Documentation/admin-guide/mm/multigen_lru.rst
+F:   Documentation/mm/multigen_lru.rst
+F:   include/linux/mm_inline.h
+F:   include/linux/mmzone.h
+F:   mm/swap.c
+F:   mm/vmscan.c
+F:   mm/workingset.c
+
 MEMORY MANAGEMENT - MISC
 M:   Andrew Morton <[email protected]>
 M:   David Hildenbrand <[email protected]>
--

2.51.0.rc1.163.g2494970778-goog

#3 lore raw
Quoted 36 lines · Axel Rasmussen
Quoted 22 lines · Shakeel Butt
Quoted 20 lines · Axel Rasmussen

The three folks being added here are actively working on MGLRU within Google, so we can review patches for this feature and plan to contribute some improvements / extensions to it on an ongoing basis.

With three of us we may have some hope filling Yu Zhao's shoes, since he has moved on to other projects these days.

---
 MAINTAINERS | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
MAINTAINERS +0 -0
index daf520a13bdf..8e987f2668cd 100644
@@ -16058,6 +16058,23 @@ F:   mm/mempolicy.c
 F:   mm/migrate.c
 F:   mm/migrate_device.c
 
Quoted 5 lines

MAINTAINERS F: mm/mempolicy.c · line 16061

Quoted 1 line
MAINTAINERS +1 -0
+MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU)

Why not just add yourselves (and the missing files) to the existing reclaim section? Eventually we want a single reclaim solution, so why not start with single reviewer section?

Sure, I can see the argument for that.

I suppose the case against would be, perhaps the folks already listed in the RECLAIM section don't want to additionally get e-mail for the extra files listed in this patch? (Perhaps mostly the MGLRU documentation, the rest of them aren't necessarily MGLRU specific.)

Quoted 5 lines

I don't have a strong preference either way, I think mostly I'd be interested to know Andrew's or the other reviewers' preference. Note Lorenzo suggested a separate MGLRU section here:
https://lkml.org/lkml/2025/8/14/271

I would not be too worried about folks getting emails for MGLRU. Anyways whatever Andrew decides is fine with me.

maintainer
#4 lore raw
Quoted 13 lines · On Fri, 15 Aug 2025 17:08:59 -0700 Shakeel Butt <[email protected]> wrote:
Quoted 13 lines
Quoted 5 lines
Quoted 1 line

+MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU)

Why not just add yourselves (and the missing files) to the existing reclaim section? Eventually we want a single reclaim solution, so why not start with single reviewer section?

Sure, I can see the argument for that.

I suppose the case against would be, perhaps the folks already listed in the RECLAIM section don't want to additionally get e-mail for the extra files listed in this patch? (Perhaps mostly the MGLRU documentation, the rest of them aren't necessarily MGLRU specific.)

Quoted 8 lines
Quoted 5 lines

I don't have a strong preference either way, I think mostly I'd be interested to know Andrew's or the other reviewers' preference. Note Lorenzo suggested a separate MGLRU section here:
https://lkml.org/lkml/2025/8/14/271

I would not be too worried about folks getting emails for MGLRU. Anyways whatever Andrew decides is fine with me.

We all like lots of emails, don't we?

I don't know, the main thing is to get it in there - we can fine-tune things later if desired.