From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1794446236; b=gCFAjr90DQGtFP22BIrY0a7xq1V/eqAnkutMFrAuuMYMfLe0DnJHQW6HGPJwUaX+JowA PcHt1z5s/WmeH0N5Dv1VZunKe/xd/yk5sKbqtP1c0w4PzwFKlB9RNZfR2K0ovfI/TA57b qJM7nkcUkXS1K12cWJ0cbgplkDKvHNkcZRUcTe34D6dq5UQTO3xyKB5oJeRXieBWfPwy7 UgtLCrBBtUVWxi6+a9AbFlCxJ5n8MuAIPPGErAW46Za15yCx2k7MZoZvnbPyNdtCLV3ym 5f0YZ0fMYLCyvY1MttIJ4n5sk0/Q4QT7jaEvcxEE5SMFid6yTtH2MlQQYH1NuSZbgcQ== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1794446236; h=Received:DKIM-Signature:Date:To:From:Subject:Message-Id; bh=9HW9unW2zAKCONCZIzBfDxesNDTPJzOi4wgIU2+7A+Y=; b=Rywpax7BYwVTfw6dwMdrJ591Rf+PZAJHrpyj3bYCBO/jheZTAlxPMyBpgaJO5ywtnbrs eaZgNvzFXzkXGpYKTIppiJErAlAhK4x8rS7bjzUnNoo3h27FLyvoV3X+rvFMJ5BlzL7FT 1G6xYGXjeF/mSuodrUkJT9zoDAC+Lr77SurVTzwx06AvrN6kR6tem7DCoH3oJHoKY7LgM YAEf7bqe6F9JJdJ5+ZTIa5nATwUV63fTmzeALW1kqQuAI5yj7tijZihGYiDx92pXT3Ys/ Oqbb5pat/rz8g1lNY2Ls24DtFvZj4+1EA3ib1Cm+4r2T6Z0PVRPo2tm7lOaceG05zSA== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linux-foundation.org header.i=@linux-foundation.org header.a=rsa-sha256 header.s=korg header.b=F+nuzk0x; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9B5A0606A324 for ; Thu, 12 Nov 2026 01:17:16 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux-foundation.org header.i=@linux-foundation.org header.a=rsa-sha256 header.s=korg header.b=F+nuzk0x Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6DBC51F00A05; Thu, 12 Nov 2026 01:17:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux-foundation.org; s=korg; t=1794446236; bh=9HW9unW2zAKCONCZIzBfDxesNDTPJzOi4wgIU2+7A+Y=; h=Date:To:From:Subject; b=F+nuzk0xGgwyMFQbsMcEKVfTMz0vfXTSTqTo6i5v665fvBlcMN8NrNNDY1zx6or7m fK0F5Ox7vYUtJPMLvEiTzpRY0no6DqiNG+kCbgf+Rwr6zzvFz89uhNVZvJPgvlZ+HH Og5mGNZHvf20l82ITMTxJqojyhtZFldZRHeF5eLs= Date: Wed, 11 Nov 2026 17:17:16 -0800 To: mm-commits@vger.kernel.org,zhuhui@kylinos.cn,zhangbo56@xiaomi.com, yuanchu@google.com,weixugc@google.com,wangzicheng@honor.com, surenb@google.com,sidchintamaneni@gmail.com,shakeel.butt@linux.dev, ryncsn@gmail.com,rppt@kernel.org,ridong.chen@linux.dev,qi.zheng@linux.dev, mhocko@suse.com,lyugaofei@xiaomi.com,liuxiang.277@bytedance.com, lianux.mm@gmail.com,liam@infradead.org,kunwu.chan@gmail.com, hui.zhu@linux.dev,hannes@cmpxchg.org,chentao@kylinos.cn,baoquan.he@linux.dev, baolin.wang@linux.alibaba.com,baohua@kernel.org,axelrasmussen@google.com, kasong@tencent.com,akpm@linux-foundation.org From: Andrew Morton Subject: + mm-mglru-lift-youngest-gen-protection-for-higher-priority.patch added to mm-new branch Message-Id: <20261112011716.6DBC51F00A05@smtp.kernel.org> X-Mailing-List: mm-commits@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list The patch titled Subject: mm/mglru: lift youngest gen protection for higher priority has been added to the -mm mm-new branch. Its filename is mm-mglru-lift-youngest-gen-protection-for-higher-priority.patch This patch will shortly appear at https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-mglru-lift-youngest-gen-protection-for-higher-priority.patch This patch will later appear in the mm-new branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm Note, mm-new is a provisional staging ground for work-in-progress patches, and acceptance into mm-new is a notification for others take notice and to finish up reviews. Please do not hesitate to respond to review feedback and post updated versions to replace or incrementally fixup patches in mm-new. The mm-new branch of mm.git is not included in linux-next If a few days of testing in mm-new is successful, the patch will me moved into mm.git's mm-unstable branch, which is included in linux-next Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/process/submit-checklist.rst when testing your code *** The -mm tree is included into linux-next via various branches at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm and is updated there most days ------------------------------------------------------ From: Kairui Song Subject: mm/mglru: lift youngest gen protection for higher priority Date: Thu, 12 Nov 2026 07:25:55 +0800 The forced protection of younger generations contradicts the goal of minimizing the I/O cost of reclaim. Under high memory pressure, MGLRU can repeatedly trigger premature OOMs, while the classic LRU does not. The problem is that aging may fail to keep up with reclaim. When this happens, reclaimers may all abort prematurely because they see only empty generations or just two generations remaining. Proactive aging does not solve this problem either. The number of threads performing proactive aging is limited, while the number of concurrent reclaimers can be much larger. This is a fundamental limitation of MGLRU. One possible solution is to use an aging lock. However, the aging lock introduces significant jitter under heavy memory pressure and has been reported to cause noticeable lags on Android. Furthermore, the generation-based reclaim model can conflict with the goal of swappiness, which is to minimize I/O cost rather than blindly follow folio hotness. The previous commit allowed reclaimers running at non-default priorities to reclaim up to `lrugen->max_seq`, while reclaimers at the default priority could reclaim only up to `lrugen->min_seq`. This patch further refines generation protection based on reclaim priority. At the default priority, reclaimers can reclaim generations down to `lrugen->min_seq - MIN_NR_GENS`. As reclaim priority increases, reclaimers are progressively allowed to reclaim younger generations. With this graduated protection, premature OOMs are no longer observed, while swappiness is also respected. Link: https://lore.kernel.org/20261111232603.9934-9-baohua@kernel.org Signed-off-by: Kairui Song Signed-off-by: Barry Song (Xiaomi) Signed-off-by: Andrew Morton Reviewed-by: Kunwu Chan Cc: Axel Rasmussen Cc: Baolin Wang Cc: Baoquan He Cc: Johannes Weiner Cc: Cc: Liam R. Howlett Cc: wang lian Cc: Cc: Cc: Michal Hocko Cc: Qi Zheng Cc: Ridong Chen Cc: Mike Rapoport Cc: Kairui Song Cc: Shakeel Butt Cc: Suren Baghdasaryan Cc: wangzicheng Cc: Wei Xu Cc: Yuanchu Xie Cc: Bo Zhang Cc: Hui Zhu Cc: Siddharth Chintamaneni Cc: Kunwu Chan --- mm/vmscan.c | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) --- a/mm/vmscan.c~mm-mglru-lift-youngest-gen-protection-for-higher-priority +++ a/mm/vmscan.c @@ -4774,12 +4774,14 @@ static int scan_folios(unsigned long nr_ VM_WARN_ON_ONCE(!list_empty(list)); /* - * Respect the gen hotness distribution at low priority to avoid - * aging and scan cost, but prefer to satisfy the reclaimers request - * when under pressure to respect swappiness more and reduce IO cost. + * Respect hotness at default priority, and only reach into the + * newest generation when under severe pressure, so hot folios are + * not evicted as soon as priority is raised. */ if (sc->priority == DEF_PRIORITY) - seq = lrugen->min_seq[type]; + seq = lrugen->max_seq - MIN_NR_GENS; + else if (sc->priority > DEF_PRIORITY / 2) + seq = lrugen->max_seq - 1; else seq = lrugen->max_seq; _ Patches currently in -mm which might be from kasong@tencent.com are mm-mglru-report-evictable-sizes-per-type.patch mm-mglru-extract-lruvec_populated_min_seq-helper.patch mm-mglru-reclaim-from-the-oldest-populated-gen.patch mm-mglru-lift-the-forced-protection-of-reclaimer.patch mm-mglru-skip-zones-above-reclaim_idx-instead-of-rotating-them.patch mm-mglru-return-for-unavailable-anon-reclaim-earlier.patch mm-mglru-balance-anon-and-file-scan-budget-by-refault-rate.patch mm-mglru-lift-youngest-gen-protection-for-higher-priority.patch