Skip to contentSkip to conversation

mm-memcg-mem_cgroup_per_node-is-already-set-to-0-on-allocation.patch removed from -mm tree

merged Andrew Morton 1 participant 1 message Mar 25, 2022

lore
Share & tools
lore

Andrew Morton

author tree notice Applied
#0 lore raw

The patch titled
Subject: mm/memcg: mem_cgroup_per_node is already set to 0 on allocation
has been removed from the -mm tree. Its filename was
mm-memcg-mem_cgroup_per_node-is-already-set-to-0-on-allocation.patch

This patch was dropped because it was merged into mainline or a subsystem tree

------------------------------------------------------
From: Wei Yang <[email protected]>
Subject: mm/memcg: mem_cgroup_per_node is already set to 0 on allocation

kzalloc_node() would set data to 0, so it's not necessary to set it again.

---

 mm/memcontrol.c |    2 --
 1 file changed, 2 deletions(-)
mm/memcontrol.c renamed from mm/memcontrol.c~mm-memcg-mem_cgroup_per_node-is-already-set-to-0-on-allocation +0 -2
@@ -5105,8 +5105,6 @@ static int alloc_mem_cgroup_per_node_inf
 	}
 
 	lruvec_init(&pn->lruvec);
-	pn->usage_in_excess = 0;
-	pn->on_tree = false;
 	pn->memcg = memcg;
 
 	memcg->nodeinfo[node] = pn;

_

Patches currently in -mm which might be from [email protected] are

mm-page_alloc-add-same-penalty-is-enough-to-get-round-robin-order.patch mm-page_alloc-add-penalty-to-local_node.patch