From: Shakeel Butt <shakeel.butt@linux.dev>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Muchun Song <muchun.song@linux.dev>, Tejun Heo <tj@kernel.org>,
Meta kernel team <kernel-team@meta.com>,
cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: [PATCH for-7.5 5/5] memcg: simplify high limit handling after a charge
Date: Sat, 10 Oct 2026 14:09:57 -0700 [thread overview]
Message-ID: <20261010210957.1350874-6-shakeel.butt@linux.dev> (raw)
In-Reply-To: <20261010210957.1350874-1-shakeel.butt@linux.dev>
Separate the hierarchy scan from high-limit enforcement. Find the first
cgroup over the applicable limit, then queue high_work or record the
task's overage after the scan. Worker contexts check only memory.high;
local charges also check memory.swap.high.
Read in_task() once and clarify the enforcement comments. Keep the
synchronous pending-overage check independent of the scan result so a
blocking charge still handles overage left by earlier charges.
No functional change intended.
Signed-off-by: Shakeel Butt <shakeel.butt@linux.dev>
---
mm/memcontrol.c | 100 +++++++++++++++++++++---------------------------
1 file changed, 43 insertions(+), 57 deletions(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index d1e022e6572f..2a3742036b45 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -2602,9 +2602,8 @@ static unsigned long calculate_high_delay(unsigned int nr_pages,
}
/*
- * Reclaims memory over the high limit. Called directly from
- * try_charge() (context permitting), as well as from the userland
- * return path where reclaim is always able to block.
+ * Handle pending high overage during a blocking charge or on return
+ * to userspace.
*/
void __mem_cgroup_handle_over_high(gfp_t gfp_mask)
{
@@ -2704,78 +2703,65 @@ void __mem_cgroup_handle_over_high(gfp_t gfp_mask)
static void memcg_enforce_high(struct mem_cgroup *memcg, unsigned int nr_pages,
gfp_t gfp_mask)
{
+ struct mem_cgroup *iter;
bool allow_spinning = gfpflags_allow_spinning(gfp_mask);
- bool use_worker = !in_task() || (current->flags & PF_KTHREAD) ||
- !current->mm || !mm_match_cgroup(current->mm, memcg);
+ bool task_context = in_task();
+ bool kthread = task_context && (current->flags & PF_KTHREAD);
+ bool use_high_work = !task_context || kthread || !current->mm ||
+ !mm_match_cgroup(current->mm, memcg);
/*
* Reclaim can charge memory, for example when zswap stores a page.
* Don't queue high_work from a reclaiming task, or the
* high_work worker could keep queuing itself.
*/
- if (in_task() && use_worker && (current->flags & PF_MEMALLOC))
+ if (task_context && use_high_work && (current->flags & PF_MEMALLOC))
return;
/*
- * If the hierarchy is above the normal consumption range, schedule
- * reclaim on returning to userland. We can perform reclaim here
- * if __GFP_RECLAIM but let's always punt for simplicity and so that
- * GFP_KERNEL can consistently be used during reclaim. @memcg is
- * not recorded as it most likely matches current's and won't
- * change in the meantime. As high limit is checked again before
- * reclaim, the cost of mismatch is negligible.
+ * Check the charged cgroup and its parents. Local charges normally defer
+ * reclaim until return to userspace so it can use GFP_KERNEL. Large
+ * pending overages may be handled synchronously below. The handler looks
+ * up current->mm and rechecks the limits.
*/
- do {
+ for (iter = memcg; iter; iter = parent_mem_cgroup(iter)) {
bool mem_high, swap_high;
- mem_high = page_counter_read(&memcg->memory) >
- READ_ONCE(memcg->memory.high);
- swap_high = page_counter_read(&memcg->swap) >
- READ_ONCE(memcg->swap.high);
-
- /*
- * Don't make an unrelated interrupted task handle this charge.
- * Kernel threads may be working for other tasks, so let a worker
- * reclaim instead.
- * Remote charges need reclaim from their charged hierarchy.
- */
- if (use_worker) {
- if (mem_high) {
- if (allow_spinning)
- schedule_work(&memcg->high_work);
- else
- irq_work_queue(&memcg->high_irq_work);
- break;
- }
- continue;
- }
-
- if (mem_high || swap_high) {
- /*
- * The allocating tasks in this cgroup will need to do
- * reclaim or be throttled to prevent further growth
- * of the memory or swap footprints.
- *
- * Target some best-effort fairness between the tasks,
- * and distribute reclaim work and delay penalties
- * based on how much each task is actually allocating.
- */
- current->memcg_nr_pages_over_high += nr_pages;
- set_notify_resume(current);
+ mem_high = page_counter_read(&iter->memory) >
+ READ_ONCE(iter->memory.high);
+ swap_high = !use_high_work &&
+ (page_counter_read(&iter->swap) > READ_ONCE(iter->swap.high));
+ if (mem_high || swap_high)
break;
- }
- } while ((memcg = parent_mem_cgroup(memcg)));
+ }
- /* Interrupts, kernel threads, and remote chargers stop here. */
- if (use_worker)
+ /*
+ * Use a worker for interrupts, kernel threads, and tasks whose mm
+ * does not match the charged hierarchy.
+ */
+ if (use_high_work) {
+ if (!iter)
+ return;
+ if (allow_spinning)
+ schedule_work(&iter->high_work);
+ else
+ irq_work_queue(&iter->high_irq_work);
return;
+ }
+
+ if (iter) {
+ /*
+ * Count the full batch so reclaim work and delay penalties scale
+ * with the pages charged by this task.
+ */
+ current->memcg_nr_pages_over_high += nr_pages;
+ set_notify_resume(current);
+ }
/*
- * Reclaim is set up above to be called from the userland
- * return path. But also attempt synchronous reclaim to avoid
- * excessive overrun while the task is still inside the
- * kernel. If this is successful, the return path will see it
- * when it rechecks the overage and simply bail out.
+ * Earlier charges may have left high overage pending even if this charge
+ * found no new overage. Handle it now if this charge can block, to limit
+ * overrun while the task remains in the kernel.
*/
if (current->memcg_nr_pages_over_high > MEMCG_CHARGE_BATCH &&
!(current->flags & PF_MEMALLOC) &&
--
2.53.0-Meta
prev parent reply other threads:[~2026-10-10 21:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 21:09 [PATCH for-7.5 0/5] memcg: clean up memory.high enforcement Shakeel Butt
2026-10-10 21:09 ` [PATCH for-7.5 1/5] memcg: move memory.high enforcement out of try_charge_memcg() Shakeel Butt
2026-10-12 13:22 ` Harry Yoo
2026-10-12 17:13 ` Shakeel Butt
2026-10-10 21:09 ` [PATCH for-7.5 2/5] memcg: use high_work for kernel threads Shakeel Butt
2026-10-10 21:09 ` [PATCH for-7.5 3/5] memcg: use high_work for remote charges Shakeel Butt
2026-10-10 21:09 ` [PATCH for-7.5 4/5] memcg: avoid queuing high_work from reclaim Shakeel Butt
2026-10-10 21:09 ` Shakeel Butt [this message]
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=20261010210957.1350874-6-shakeel.butt@linux.dev \
--to=shakeel.butt@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=tj@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.