From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,sj@kernel.org,shakeel.butt@linux.dev,mhocko@suse.com,gourry@gourry.net,lihongfu@kylinos.cn,akpm@linux-foundation.org
Subject: [merged mm-stable] mm-memcontrol-remove-unused-memcg-parameter-in-calculate_high_delay.patch removed from -mm tree
Date: Tue, 06 Oct 2026 17:49:01 -0700 [thread overview]
Message-ID: <20261007004902.0C3E51F0089C@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/memcontrol: remove unused memcg parameter in calculate_high_delay()
has been removed from the -mm tree. Its filename was
mm-memcontrol-remove-unused-memcg-parameter-in-calculate_high_delay.patch
This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Hongfu Li <lihongfu@kylinos.cn>
Subject: mm/memcontrol: remove unused memcg parameter in calculate_high_delay()
Date: Tue, 25 Aug 2026 20:01:53 +0800
The memcg argument of calculate_high_delay() is never referenced in its
function body. The delay calculation only depends on nr_pages and
max_overage, and both callers have already obtained max_overage from the
same memcg.
Drop this unused parameter and update the two call sites inside
__mem_cgroup_handle_over_high().
Link: https://lore.kernel.org/20260825120153.1405-1-hongfu.li@linux.dev
Signed-off-by: Hongfu Li <lihongfu@kylinos.cn>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Acked-by: Michal Hocko <mhocko@suse.com>
Reviewed-by: Gregory Price (Meta) <gourry@gourry.net>
Reviewed-by: SJ Park <sj@kernel.org>
Acked-by: Shakeel Butt <shakeel.butt@linux.dev>
---
mm/memcontrol.c | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
--- a/mm/memcontrol.c~mm-memcontrol-remove-unused-memcg-parameter-in-calculate_high_delay
+++ a/mm/memcontrol.c
@@ -2515,8 +2515,7 @@ static u64 swap_find_max_overage(struct
* Get the number of jiffies that we should penalise a mischievous cgroup which
* is exceeding its memory.high by checking both it and its ancestors.
*/
-static unsigned long calculate_high_delay(struct mem_cgroup *memcg,
- unsigned int nr_pages,
+static unsigned long calculate_high_delay(unsigned int nr_pages,
u64 max_overage)
{
unsigned long penalty_jiffies;
@@ -2594,10 +2593,10 @@ retry_reclaim:
* memory.high is breached and reclaim is unable to keep up. Throttle
* allocators proactively to slow down excessive growth.
*/
- penalty_jiffies = calculate_high_delay(memcg, nr_pages,
+ penalty_jiffies = calculate_high_delay(nr_pages,
mem_find_max_overage(memcg));
- penalty_jiffies += calculate_high_delay(memcg, nr_pages,
+ penalty_jiffies += calculate_high_delay(nr_pages,
swap_find_max_overage(memcg));
/*
_
Patches currently in -mm which might be from lihongfu@kylinos.cn are
mm-page_owner-preserve-original-free_pid-free_tgid-during-folio-migration.patch
mm-memfd-fix-hugetlb-reservation-accounting-in-error-paths.patch
selftests-mm-fix-ptrace-peekdata-check-in-memfd_secret-test.patch
mm-hugetlb_cgroup-move-per-node-usage-on-cross-node-migration.patch
mm-hugetlb_cgroup-move-per-node-usage-on-cgroup-reparenting.patch
mm-hugetlb-account-migration-target-folio-in-per-node-nr_hugetlb-vmstat.patch
mm-memcg-migrate-per-node-hugetlb-lruvec-stat-together-with-hugetlb-folio.patch
reply other threads:[~2026-10-07 0:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261007004902.0C3E51F0089C@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=gourry@gourry.net \
--cc=lihongfu@kylinos.cn \
--cc=mhocko@suse.com \
--cc=mm-commits@vger.kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=sj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.