Re: [PATCH v3] mm/vmpressure: skip socket pressure for costly order reclaim

[JP Kobryn (Meta)]

On 4/6/26 10:54 AM, Andrew Morton wrote:
> On Mon,  6 Apr 2026 10:44:25 -0700 "JP Kobryn (Meta)" <jp.kobryn@xxxxxxxxx> wrote:
>
> > When reclaim is triggered by high order allocations on a fragmented system,
> > vmpressure() can report poor reclaim efficiency even though the system has
> > plenty of free memory. This is because many pages are scanned, but few are
> > found to actually reclaim - the pages are actively in use and don't need to
> > be freed. The resulting scan:reclaim ratio causes vmpressure() to assert
> > socket pressure, throttling TCP throughput unnecessarily.
> >
> > Costly order allocations (above PAGE_ALLOC_COSTLY_ORDER) rely heavily on
> > compaction to succeed, so poor reclaim efficiency at these orders does not
> > necessarily indicate memory pressure. The kernel already treats this order
> > as the boundary where reclaim is no longer expected to succeed and
> > compaction may take over.
> >
> > Make vmpressure() order-aware through an additional parameter sourced from
> > scan_control at existing call sites. Socket pressure is now only asserted
> > when order <= PAGE_ALLOC_COSTLY_ORDER.
> >
> > Memcg reclaim is unaffected since try_to_free_mem_cgroup_pages() always
> > uses order 0, which passes the filter unconditionally. Similarly,
> > vmpressure_prio() now passes order 0 internally when calling vmpressure(),
> > ensuring critical pressure from low reclaim priority is not suppressed by
> > the order filter.
>
> Thanks.  I'd prefer to park this until after next -rc1.  I could be
> argued with, but....
>
> What I'm not understanding from the above is how beneficial this patch
> is.  Some description of observed before-and-after behavior, preferably
> with impressive measurements?

Let me know if this data helps, and if you'd like this added to the
changelog.

On one affected host with impacted net throughput, the memory state at
the time showed ~15GB available, zero cgroup pressure, and the following
buddyinfo state:

Order FreePages
0:    133,970
1:    29,230
2:    17,351
3:    18,984
7+:   0

Using bpf, it was found that 94% of vmpressure calls on this host were
from order-7 kswapd reclaim.

TCP minimum recv window is rcv_ssthresh:19712.

Before patch:
723 out of 3,843 (19%) TCP connections stuck at minimum recv window

After live-patching and ~30min elapsed:
0 out of 3,470 TCP connections stuck at minimum recv window