[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aBshiBX_N6hhExmS@pc636>
Date: Wed, 7 May 2025 11:02:00 +0200
From: Uladzislau Rezki <urezki@...il.com>
To: David Hildenbrand <david@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
Jason Gunthorpe <jgg@...dia.com>,
John Hubbard <jhubbard@...dia.com>, Peter Xu <peterx@...hat.com>,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add mm GUP section
On Wed, May 07, 2025 at 10:05:58AM +0200, David Hildenbrand wrote:
> On 07.05.25 01:21, Andrew Morton wrote:
> > On Tue, 6 May 2025 18:36:01 +0100 Lorenzo Stoakes <lorenzo.stoakes@...cle.com> wrote:
> >
> > > As part of the ongoing efforts to sub-divide memory management
> > > maintainership and reviewership, establish a section for GUP (Get User
> > > Pages) support and add appropriate maintainers and reviewers.
> > >
> >
> > Thanks, I was wondering about that.
>
> Thanks Lorenzo for driving this!
>
> Acked-by: David Hildenbrand <david@...hat.com>
>
> >
> > (looks at vmscan.c)
>
> Current maintainers (mm/unstable) on 20 biggest files in mm, Andrew is
> implicit:
>
> $ find mm -name "*.c" -type f | xargs wc -l | sort -n -r | head -20
> 198195 total
> 7937 mm/hugetlb.c # Muchun
> 7881 mm/slub.c # Christoph/David/Vlastimil
> 7745 mm/vmscan.c #
> 7424 mm/page_alloc.c #
> 7166 mm/memory.c # David
> 5962 mm/shmem.c # Hugh
> 5553 mm/memcontrol.c # Johannes/Roman/Shakeel
> 5245 mm/vmalloc.c #
> 4703 mm/huge_memory.c # David
> 4538 mm/filemap.c # Willy
> 3964 mm/swapfile.c #
> 3871 mm/ksm.c #
> 3720 mm/gup.c # David
> 3675 mm/mempolicy.c #
> 3371 mm/percpu.c # Dennis/Tejun/Christoph
> 3370 mm/compaction.c #
> 3197 mm/page-writeback.c # Willy
> 3097 mm/vma.c # Liam/Lorenzo
> 2988 mm/rmap.c # David/Lorenzo
>
> I've been messing with KSM for a long time, so I could easily jump in as
> maintainer for that. Probably we want page migration (incl. mempolicy?) as a
> separate entry. I've been messing with that as well (and will be messing
> more), so I could jump in for that as well.
>
> For page allocator stuff (incl. compaction) we at least have plenty of
> reviewers now. For vmalloc we at least have Uladzislau as single reviewer.
>
> vmscan.c and vmalloc.c really need some love.
>
As for "vmalloc.c" i can jump in as an extra maintainer aside with
Andrew if no objections.
--
Uladzislau Rezki
Powered by blists - more mailing lists