From: Axel Rasmussen <axelrasmussen@google.com>
To: Shakeel Butt <shakeel.butt@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Yuanchu Xie <yuanchu@google.com>, Wei Xu <weixugc@google.com>,
Yu Zhao <yuzhao@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: mark MGLRU as maintained
Date: Fri, 15 Aug 2025 16:40:26 -0700 [thread overview]
Message-ID: <CAJHvVchYa-vUcQo92awyHE663n-iMsLK31o+1FKrMvdLMAuUOg@mail.gmail.com> (raw)
In-Reply-To: <7a46f7jwlwgkbdjvbxjaalrrdamgtxkptmytllhkr2qv4ovbge@nbugfzavwh5w>
On Fri, Aug 15, 2025 at 4:13 PM Shakeel Butt <shakeel.butt@linux.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@google.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@linux-foundation.org>
> > +M: Axel Rasmussen <axelrasmussen@google.com>
> > +M: Yuanchu Xie <yuanchu@google.com>
> > +R: Wei Xu <weixugc@google.com>
> > +L: linux-mm@kvack.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@linux-foundation.org>
> > M: David Hildenbrand <david@redhat.com>
> > --
> > 2.51.0.rc1.163.g2494970778-goog
> >
next prev parent reply other threads:[~2025-08-15 23:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 21:59 Axel Rasmussen
2025-08-15 23:13 ` Shakeel Butt
2025-08-15 23:40 ` Axel Rasmussen [this message]
2025-08-16 0:08 ` Shakeel Butt
2025-08-16 5:32 ` Andrew Morton
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=CAJHvVchYa-vUcQo92awyHE663n-iMsLK31o+1FKrMvdLMAuUOg@mail.gmail.com \
--to=axelrasmussen@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shakeel.butt@linux.dev \
--cc=weixugc@google.com \
--cc=yuanchu@google.com \
--cc=yuzhao@google.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