Re: [PATCH v6 0/3] mm: Free contiguous order-0 pages efficiently

Johannes Weiner
2026-04-29T13:52:34Z

On Wed, Apr 29, 2026 at 01:31:10PM +0100, Ryan Roberts wrote:
> On 29/04/2026 13:04, Andrew Morton wrote:
> > On Wed, 29 Apr 2026 06:33:26 -0400 Johannes Weiner <hannes@cmpxchg.org> wrote:
> >
> >> On Wed, Apr 01, 2026 at 11:16:18AM +0100, Muhammad Usama Anjum wrote:
> >>> Hi All,
> >>>
> >>> A recent change to vmalloc caused some performance benchmark regressions (see
> >>> [1]). I'm attempting to fix that (and at the same time significantly improve
> >>> beyond the baseline) by freeing a contiguous set of order-0 pages as a batch.
> >>
> >> I think we should revert the original patch.
> >>
> >> The premise is that we can save some allocator calls by requesting
> >> higher orders and splitting them up into singles. This is a frivolous
> >> and short-sighted use of a very coveted and expensive resource.
>
> I'm not sure it's that simple. First off, vmalloc has preferred to allocate high
> order pages for quite a while, it's just that the patch you're referring to
> makes it try even harder. So reverting the patch doesn't completely revert the
> behaviour, it just reduces it.
>
> Performance benefits because those high order pages are mapped appropriately in
> the page table - i.e. 1G PUD, 2M PMD, (or 64K CONTPTE on arm64). So it's not
> solely about the number of cycles spent in the allocator; the HW is used more
> efficiently. vmalloc only splits to order-0 for the benefit of the caller,
> because there are some places that assume they can access each returned struct page.

Sure, TLB benefits can offset the cost.

PTE mapped higher orders on systems without contpte (still many) are the problem.

> And all the order-0 pages of the original high order page are freed at the same
> time, so it's not like we are destroying the contiguous resource; it remains
> intact for the next user (well, ignoring that some will be freed to the pcpu
> list - this series solves that wrinkle). I've heard it argued that this approach
> is actually _better_ for conserving contiguous blocks because it's keeping the
> lifetime of all the constituent pages bound together and reducing fragmentation.

You're still consuming contiguity and increasing competition over
it. That needs to pay off in a closed system, not just in one small
part of it.

I'm a bit skeptical of that beneficial effect. Sure, if there aren't
any small fragments and most everybody is doing larger allocations,
then yes, this could make sense. Although in that case, even calling
the buddy allocator repeatedly from vmalloc would give you physically
adjacent pages due to the way splitting works (although I'm not sure
right now if you'd get the right exact PFN order for contpte).

But as long as there is a mix of allocation sizes with mixed
lifetimes, consuming contiguity that you don't need has a high cost
over vacuuming up holes and fragments. Because now you're competing
with somebody who has no choice but to *painstakingly move live pages
around to coalesce the holes*.

That's the whole reason for the __rmqueue_smallest()-first policy in
the page allocator. It's fine for somebody to challenge this. But it
feels pretty strange to make a unilateral decision in vmalloc that
works around and inverts established allocator policy, with very
little data to boot.

> I've never seen any data though...

Yes. Considering the possible externalities of this patch, IMO we
should have much more data on big picture behavior, under varying
pressure situations and workloads etc.

The reason for my email was that we see this hurting in experiments
with new code. The vmalloc higher-orders cause a sharp increase in
compaction activity, subsequent lock contention in zsmalloc migration
callbacks etc. I wasn't just making this up.