Re: [RFC PATCH 00/57] mm/collapse: rebuild collapse on migration primitives

(I'll reply to the rest of this later)

On Mon, Aug 17, 2026 at 02:38:44PM +0100, Kiryl Shutsemau wrote:

David and I talked about this at LSF/MM.  I can give it a try if it fits
your idea of "feature freeze" -- and if it doesn't collide with the series
you have in flight, in which case I'd rather go after yours than around it.

Whether intended or not you sound rather like you are trying to override me
in favour of my co-maintainer here and it's... not helpful.

David and I co-maintain THP together, are in constant communication, and
have a great working relationship :)

IOW - if one of us states a position on the sub(sub?)system - then take
that to be the actual position.

I have poured what must be hundreds of hours now into THP maintainership -
it's by far my biggest workload on the maintenance front, by far the most
painful and by far the most thankless.

I do it because I care about mm a great deal and am, frankly, driven by a
desire to see THP turn from a flaming trash pile of a code base with
confusing semantics and many, many broken parts into something that serves
the community's needs with far less maintenance burden.

Looking over your series it seems some of the patches works in this
direction (great!), but much else of it fundamentally changes key
behaviour.

So it's just a question of deferring the latter until we get to a sane
point with the former.

I keep talking about this stuff because companies are motivated by wanting
to solve their problems (understandably) but if nobody pushes back then THP
will continue to be a series of changes lumped on top of one another adding
more and more technical debt.

--
Cheers, Lorenzo