From: Vlastimil Babka <vbabka@suse.cz>
To: David Hildenbrand <david@redhat.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: "Liam R . Howlett" <Liam.Howlett@oracle.com>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] MAINTAINERS: add further core files to mm core section
Date: Tue, 17 Jun 2025 20:47:07 +0200 [thread overview]
Message-ID: <d59ff240-bb46-47e5-92ad-fd2d9c1a9f42@suse.cz> (raw)
In-Reply-To: <727b5e89-89d7-4abf-a93c-8d6f2cb2c438@redhat.com>
On 6/16/25 23:10, David Hildenbrand wrote:
> On 16.06.25 22:38, Lorenzo Stoakes wrote:
>> There are a number of files which don't quite belong anywhere else, so
>> place them in the core section. If we determine in future they belong
>> elsewhere we can update incrementally but it is preferable that we assign
>> each file to a section as best we can.
>>
>> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
>> ---
>> REVIEWERS - let me know if these seem appropriate, I'm eyeballing
>> this. even if they are not quite best placed a 'best effort' is still
>> worthwhile so we establish a place to put all mm files, we can always
>> incrementally update these later.
>> @@ -15764,16 +15760,40 @@ S: Maintained
>> W: http://www.linux-mm.org
>> T: git git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
>> F: include/linux/memory.h
>> +F: include/linux/memremap.h
>> F: include/linux/mm.h
>> F: include/linux/mm_*.h
>> F: include/linux/mmdebug.h
>> +F: include/linux/mmu_notifier.h
>> +F: include/linux/mmzone.h
>> F: include/linux/pagewalk.h
>> F: kernel/fork.c
>> F: mm/Kconfig
>> F: mm/debug.c
>> +F: mm/debug_page_ref.c
>> +F: mm/debug_vm_pgtable.c
>
> Wondering if there should be a MM DEBUG section. But then, no idea who
> in their right mind would be willing to maintain that ;)
Guess I'm not in my right mind, but I'd be fine with that. Although most of
my experience is with page_owner and debug_pagealloc which are tied to the
page allocator. And I think it's better when these debug files are in the
section of the functionality they debug. mm/debug_page_ref.c could probably
go to the page allocator. mm/debug_vm_pgtable.c is maybe related to
pagewalk? (it could be redone to a kunit test, btw?). Only mm/debug.c seems
a mix of stuff related to various mm parts... maybe could stay in core then.
prev parent reply other threads:[~2025-06-17 18:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 20:38 Lorenzo Stoakes
2025-06-16 21:10 ` David Hildenbrand
2025-06-16 22:56 ` Shakeel Butt
2025-06-17 15:22 ` Lorenzo Stoakes
2025-06-17 17:51 ` Shakeel Butt
2025-06-17 17:55 ` Lorenzo Stoakes
2025-06-17 3:53 ` Mike Rapoport
2025-06-17 7:59 ` David Hildenbrand
2025-06-17 15:04 ` Lorenzo Stoakes
2025-06-17 15:46 ` David Hildenbrand
2025-07-22 13:53 ` Lorenzo Stoakes
2025-07-22 14:22 ` Vlastimil Babka
2025-07-23 5:36 ` Christoph Hellwig
2025-06-17 15:26 ` Lorenzo Stoakes
2025-06-19 5:31 ` Alistair Popple
2025-06-17 18:47 ` Vlastimil Babka [this message]
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=d59ff240-bb46-47e5-92ad-fd2d9c1a9f42@suse.cz \
--to=vbabka@suse.cz \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=surenb@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