linux-kernel - Re: [PATCH] MAINTAINERS: mark MGLRU as maintained

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJHvVchYa-vUcQo92awyHE663n-iMsLK31o+1FKrMvdLMAuUOg@mail.gmail.com>
Date: Fri, 15 Aug 2025 16:40:26 -0700
From: Axel Rasmussen <axelrasmussen@...gle.com>
To: Shakeel Butt <shakeel.butt@...ux.dev>
Cc: Andrew Morton <akpm@...ux-foundation.org>, Yuanchu Xie <yuanchu@...gle.com>, 
	Wei Xu <weixugc@...gle.com>, Yu Zhao <yuzhao@...gle.com>, linux-mm@...ck.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: mark MGLRU as maintained

On Fri, Aug 15, 2025 at 4:13 PM Shakeel Butt <shakeel.butt@...ux.dev> wrote:
>
> On Fri, Aug 15, 2025 at 02:59:14PM -0700, Axel Rasmussen wrote:
> > 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.
> >
> > Signed-off-by: Axel Rasmussen <axelrasmussen@...gle.com>
> > ---
> >  MAINTAINERS | 17 +++++++++++++++++
> >  1 file changed, 17 insertions(+)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index daf520a13bdf..8e987f2668cd 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -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?

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

>
> > +M:   Andrew Morton <akpm@...ux-foundation.org>
> > +M:   Axel Rasmussen <axelrasmussen@...gle.com>
> > +M:   Yuanchu Xie <yuanchu@...gle.com>
> > +R:   Wei Xu <weixugc@...gle.com>
> > +L:   linux-mm@...ck.org
> > +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 <akpm@...ux-foundation.org>
> >  M:   David Hildenbrand <david@...hat.com>
> > --
> > 2.51.0.rc1.163.g2494970778-goog
> >