Re: [RFC PATCH 00/57] mm/collapse: rebuild collapse on migration primitives
Kiryl Shutsemau <[email protected]>
| Newsgroups | org.kernel.vger.linux-trace-kernel,org.kernel.vger.bpf,org.kernel.vger.linux-kernel,org.kernel.vger.linux-kselftest,org.kvack.linux-mm |
|---|---|
| Message-ID | <aoX0FF9ysdc78UFG@thinkstation> |
On Tue, Aug 18, 2026 at 03:41:40PM +0100, Lorenzo Stoakes (ARM) wrote: > > Ah, I missed the context in my other reply. Lorenzo already had some patches at > > some point to split up mm/memory.c into better chunks that will also better help > > our subcomponent maintenance model. > > Ah yeah I kinda lost those but indeed doing this is a good idea. Oh, well, I can give it a try from scratch. > I should try to dig those out again or look again when I have a chance... > > > > > I think the challenge is how to handle huge_memory.c, because ideally, we'd not > > have these stupid callbacks into huge_memory.c once we make PMDs just a > > first-class citizen. > > Yes and another point and I think it's one that Kiryl also gets at is - can we > _please_ stop pretending huge folios == THP == what the page cache does == page > special cases like DAX? :) Yes. That is also why I want the split by operation rather than by THP-ness: a PMD case belongs next to the PTE case for the same operation, not in a file that collects everything huge. -- Kiryl Shutsemau / Kirill A. Shutemov