From: Uladzislau Rezki <urezki@gmail.com>
To: David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Jason Gunthorpe <jgg@nvidia.com>,
John Hubbard <jhubbard@nvidia.com>, Peter Xu <peterx@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add mm GUP section
Date: Wed, 7 May 2025 11:02:00 +0200 [thread overview]
Message-ID: <aBshiBX_N6hhExmS@pc636> (raw)
In-Reply-To: <c4258dfd-14ee-411a-9fa7-c4a1fa4fad1c@redhat.com>
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@oracle.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@redhat.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
next prev parent reply other threads:[~2025-05-07 9:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 17:36 [PATCH] MAINTAINERS: add mm GUP section Lorenzo Stoakes
2025-05-06 17:41 ` John Hubbard
2025-05-06 23:21 ` Andrew Morton
2025-05-07 8:05 ` David Hildenbrand
2025-05-07 9:02 ` Uladzislau Rezki [this message]
2025-05-07 9:23 ` Lorenzo Stoakes
2025-05-07 9:59 ` Uladzislau Rezki
2025-05-08 8:53 ` David Hildenbrand
2025-05-08 12:23 ` Lorenzo Stoakes
2025-05-08 16:03 ` Lorenzo Stoakes
2025-05-08 17:43 ` David Hildenbrand
2025-05-08 18:50 ` Lorenzo Stoakes
2025-05-12 7:38 ` Vlastimil Babka
2025-05-12 12:54 ` Zi Yan
2025-05-12 13:01 ` David Hildenbrand
2025-05-12 13:10 ` Lorenzo Stoakes
2025-05-12 13:06 ` Lorenzo Stoakes
2025-05-13 6:23 ` Mike Rapoport
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=aBshiBX_N6hhExmS@pc636 \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=jgg@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=peterx@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.