[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <eb2b0bce-6012-4019-8ff7-c35c24ba7aa1@suse.cz>
Date: Mon, 12 May 2025 09:38:46 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
David Hildenbrand <david@...hat.com>, Zi Yan <ziy@...dia.com>
Cc: Uladzislau Rezki <urezki@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>, 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 5/8/25 14:23, Lorenzo Stoakes wrote:
>>
>> M for "PAGE ALLOCATOR", hmmm ..., I was hoping that Vlastimil might have
>> capacity for that? :)
>
> Vlastimil? ;)
>
> I'd certainly support this.
OK, can do, thanks.
>>
>>
>>
>> Not 100% sure what to do with
>>
>> * include/linux/page_isolation.h
>> * mm/page_isolation.c
>>
>> (I hate the word "page isolation")
>>
>> They are mostly about page migration (either for alloc_contig... or memory
>> hotunplug). Likely they should either go to the MIGRATION section or to the
>> PAGE ALLOCATOR? Maybe MIGRATION makes more sense. Thoughts?
>
> I mean it explicitly relates to migrate type and migration so seems to me
> it ought to be in migration.
>
> Though migrate type + the machinary around it is a product of the physical
> page allocator (I even cover it in the 'physical memory' section of the
> book).
>
> I wonder if our soon-to-be page allocator maintainer Vlastimil has
> thoughts? ;)
>
> I'd vote for migration though to be honest.
I checked the code briefly and although migratetypes are related to
migration, it seems rather page allocator code to me.
In fact if I didn't miss these files, I would have included them when
proposing the PAGE ALLOCATOR section.
Zi Yan has a series on that topic now and is one of the R: in PAGE
ALLOCATOR. What do you think?
>>
>> --
>> Cheers,
>>
>> David / dhildenb
>>
Powered by blists - more mailing lists