Skip to contentSkip to conversation

mm/memcg: mz already removed from rb_tree if not NULL

PATCH Applied Wei Yang 1 participant 1 message Mar 14, 2022

Subsystems (3)
lore
Share & tools
lore

Wei Yang

author
#0 lore raw

PATCH v3 1/1 mm/memcg: mz already removed from rb_tree if not NULL

When mz is not NULL, it means mz can either come from mem_cgroup_largest_soft_limit_node or __mem_cgroup_largest_soft_limit_nod. And both of them has removed this node by __mem_cgroup_remove_exceeded().

Not necessary to call __mem_cgroup_remove_exceeded() again.

---
 mm/memcontrol.c | 1 -
 1 file changed, 1 deletion(-)
mm/memcontrol.c +0 -1
index dc225ca512f6..e803ff02aae2 100644
@@ -3460,7 +3460,6 @@ unsigned long mem_cgroup_soft_limit_reclaim(pg_data_t *pgdat, int order,
 		nr_reclaimed += reclaimed;
 		*total_scanned += nr_scanned;
 		spin_lock_irq(&mctz->lock);
-		__mem_cgroup_remove_exceeded(mz, mctz);
 
 		/*
 		 * If we failed to reclaim anything from this memory cgroup
Signature · 1 line
2.33.1