[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d6463ac6-a27f-472b-80bf-49cb2a632302@lucifer.local>
Date: Thu, 14 Aug 2025 06:40:06 +0100
From: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Axel Rasmussen <axelrasmussen@...gle.com>,
David Hildenbrand <david@...hat.com>, Qingshuang Fu <fffsqian@....com>,
hannes@...xchg.org, mhocko@...nel.org, zhengqi.arch@...edance.com,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Qingshuang Fu <fuqingshuang@...inos.cn>,
Yuanchu Xie <yuanchu@...gle.com>
Subject: Re: [PATCH] Fix the data type inconsistency issue of min (tier,
MAX_CR_TIERS-1) in read_ctrl_pos
On Wed, Aug 13, 2025 at 02:41:45PM -0700, Andrew Morton wrote:
> On Wed, 13 Aug 2025 13:03:42 -0700 Axel Rasmussen <axelrasmussen@...gle.com> wrote:
>
> > >
> > >
> > > (cc mglru maintainers, who have yet to reveal themselves in MAINTAINERS)
> >
> > Sorry for that, I took a look at adding myself and Yuanchu, but it
> > wasn't clear how to represent MGLRU in MAINTAINERS, because there
> > isn't a mglru.c, it's bolted on to several existing files with
> > existing maintainers. Should us two just be appended to the list of
> > folks for vmscan.c, or?
>
> I think a separate MGLRU section which mentions mm/vmscan.c is
> appropriate. kernel/fork.c gets a mention in three sections.
>
Indeed, it turns out you can have multiple entries with the same file(s),
which turned out to be very useful in assigning the covers-many-bases
kernel/fork.c.
Having added a bunch of the newer mm entries, may I humbly suggest
something like:
MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU)
M: Andrew Morton <akpm@...ux-foundation.org>
M: Axel Rasmussen <axelrasmussen@...gle.com>
M: Yuanchu Xie <yuanchu@...gle.com>
< figure out any appropriate reviewers here, if any >
L: linux-mm@...ck.org
S: Maintained
F: mm/vmscan.c
Placed in the correct alphabetical location in MAINTAINERS?
Cheers, Lorenzo
Powered by blists - more mailing lists