From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mta0.migadu.com (out-234.mta0.migadu.com [91.218.175.234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 27F2F5474F for ; Thu, 20 Aug 2026 02:48:43 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.234 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787194126; cv=none; b=m4e9qhPtUWRODp7jrT1pZFOG8uqRGaZFnKv3G1G+vTM284qoaj25RrdYdUZvFAPvnKfmQuhJto0dwBXiLKvuk5yF7W1qVGoux2eVOcyU9+6+Qrm9qZw3/kGcgkU5d2ZtVz0L9rEtSYFSv9JOKd7A8PfEjC1figJ7FjA+lmeMkeY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787194126; c=relaxed/simple; bh=bKhUkXEqGv90J1vw0cE7EUs5ijqf/z30Rg7S8EZpNag=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=qMI6PquKcSnCqoN5QQL9JYjW7SUheyIRvlhS1ziKo+nCB29GbHYu3vpeU+UAtVR+o5wHD4ukGTLXpbtLPrFbn1lL8zuXeXWmJy6ygyjxVI5x6vWwz87930lhk2x/qWdOW4K+C3695B12py9QqhQsUgxUwl/9vguhDA2d9K7QrHA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=tGBAT/nE; arc=none smtp.client-ip=91.218.175.234 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="tGBAT/nE" X-Envelope-To: linux-kernel@vger.kernel.org DKIM-Signature: a=rsa-sha256; bh=bKhUkXEqGv90J1vw0cE7EUs5ijqf/z30Rg7S8EZpNag=; c=simple/simple; d=linux.dev; h=from:to:subject:date:message-id:mime-version:content-type; s=key1; t=1787194121; v=1; x=1787798921; b=tGBAT/nEIh6cHBSLsxX8/HVhYjrvT5jfvQu5Dwc3B9iER037olyxiGyGepU0G7l6Uo2hPFQo aZT3GwbjVFe0TaR/INcyDBnKLUm3jm5kJjgLih0diQK07Lx589ifpbP5PT+cCT/UB5fxF88+7Zo zZYL/ajAuqN9ha9M2E1J6jVU= X-Envelope-To: linux-kernel@vger.kernel.org Received: from teawater-KVM-Virtual-Machine (39.156.73.13) by smtp.migadu.com with ESMTPS id 164f2e45294aaef1; Thu, 20 Aug 2026 02:48:41 +0000 X-Mizu-Trace-ID: 164f2e45294aaef1 X-Migadu-Flow: FLOW_OUT From: "Hui Zhu" To: Andrew Morton , Kairui Song , Qi Zheng , Shakeel Butt , Barry Song , Axel Rasmussen , Yuanchu Xie , Wei Xu , Johannes Weiner , David Hildenbrand , Michal Hocko , Lorenzo Stoakes , Baolin Wang , linux-mm@kvack.org, linux-kernel@vger.kernel.org Cc: Hui Zhu Subject: [PATCH mm-unstable v4 0/2] mm/vmscan: fix NR_ISOLATED accounting and throttling for MGLRU Date: Thu, 20 Aug 2026 10:48:13 +0800 Message-ID: X-Mailer: git-send-email 2.53.0 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: Hui Zhu The legacy reclaim path updates the NR_ISOLATED_ANON/FILE node counters around isolation and throttles direct reclaimers via too_many_isolated() when isolated folios pile up. The MGLRU eviction path does neither: evict_folios() isolates folios without touching the counters and never consults too_many_isolated(). Patch 1 updates NR_ISOLATED_ANON/FILE around isolation in evict_folios(), reusing the existing nr_isolated. Without this the counters stay at zero while MGLRU reclaim is active, so compaction's too_many_isolated() cannot see the pages MGLRU has isolated. Patch 2 adds throttle_evictable_types() and calls it from evict_folios(), before the lruvec lock is taken since throttling sleeps, leaving the legacy path untouched. The MGLRU check differs from the legacy per-list one in shrink_inactive_list() because isolate_folios() picks the type to scan from the refault feedback and may fall back to the other one: it computes the set of evictable types that are not over-isolated and only sleeps when all of them are, waiting once for concurrent reclaimers exactly like the legacy path. The mask of the remaining types is passed to isolate_folios(), which restricts both its initial choice and its fallback to it, so isolation never lands on an over-isolated type and a type that is merely over-isolated never blocks the reclaim of the other one. This way the MGLRU eviction path backs off when isolated folios pile up instead of thrashing the shrinking LRU lists - the scenario the too_many_isolated() check exists for. A dying task fakes reclaim progress exactly like the legacy path so it exits reclaim quickly. Testing ======= Test on 8G RAM qemu. The reproducer confines stress-ng workers in a 192M memcg and swaps through dm-delay (300ms write latency) so pageout is slow and isolated folios pile up; the workload is intentionally extreme. nr_isolated_* is sampled every 50ms against the per-type too_many_isolated threshold (inactive/8), and throttle events are counted via the mm_vmscan_throttled tracepoint. The test scripts and test log are in [1]. Test 1, reclaim throttling, parallel direct reclaim in the memcg: before after throttle events (ISOLATED) 0 0 - from kswapd 0 0 nr_isolated_anon peak 0 3166 nr_isolated_file peak 0 174 - samples above the too_many_isolated threshold 0/1088 89/1077 pgscan_direct 1540044096 858332151 pswpout 6299497 725819 Without the series MGLRU reclaim spins on the shrinking LRU lists while nr_isolated_* stays at 0 and nothing is throttled: pgscan_direct runs to 1.5 billion and 6.3M pages are pushed through the 300ms swap device, i.e. the memcg anon is recycled over and over. With the series the counters are updated and the too_many_isolated threshold is crossed (89 of 1077 samples). Only anon is over-isolated in this workload, so the throttle never has to sleep: it stops reclaimers from isolating more anon and has them fall back to file instead (nr_isolated_file peaks at 174 instead of 0), and anon isolation stays around the threshold (peak 3166). Scanning drops by ~45% and the swap-out storm by ~9x: the reclaimers stop hammering the shrinking anon LRU while the slow swap device is still writing out the previous batches. kswapd stays exempt. Test 2, counters visible to compaction, same pressure plus compact_memory in parallel: before after nr_isolated peak 456 2232 The "before" 456 is compaction's own transient isolation; reclaim's isolation is invisible. With patch 1 it becomes visible to compaction's too_many_isolated(). (Compaction's own throttling threshold, (inactive + active) / 16, is about 25k pages on this box and needs more pile-up than the box can generate; test 1 shows the same too_many_isolated() check firing on the reclaim side.) [1] https://gist.github.com/teawater/d3968aac92eb6bd1378beb54a82933f4 Changelog: v4: According to the commens of Baolin and Barry, rework patch 2: drop the throttle_is_throttled() helper extracted from shrink_inactive_list() and leave the legacy path untouched. The new MGLRU-only throttle_evictable_types() only sleeps when all evictable types are over-isolated - v3 throttled as soon as any of them was, which unnecessarily blocked the reclaim of the other type and passes the mask of the remaining types to isolate_folios(), which restricts both its initial choice and its fallback, so that isolation never lands on a throttled type. The v3 gate did not constrain the type actually isolated, so the fallback could still pick the over-isolated one. Re-run the tests and update the test log. v3: According to the commens of Baolin, remove the redundant nr_isolated check before restoring the NR_ISOLATED_* counters in evict_folios(). rename the extracted helper to throttle_is_throttled() to avoid confusion with the existing wake_throttle_isolated() naming space. Use for_each_evictable_type() in the MGLRU throttle to check each evictable type's isolation instead of only the type returned by get_type_to_scan(), since isolate_folios() may fall back to the other type. Re-run the tests and update the test log. v2: According to the commens of Kairun, Rebased on mm-unstable. Split into two patches; patch 2 is new and adds the too_many_isolated() throttling to the MGLRU eviction path, which v1 did not cover. Add test infomations. Hui Zhu (2): mm/vmscan: fix missing NR_ISOLATED counter update in MGLRU reclaim path mm/vmscan: apply too_many_isolated() throttling to MGLRU eviction mm/vmscan.c | 90 ++++++++++++++++++++++++++++++++++++++++++++++++++--- 1 file changed, 85 insertions(+), 5 deletions(-) -- 2.53.0