[034/227] mm/memcg: mem_cgroup_per_node is already set to 0 on allocation

Commit Message

Andrew Morton March 22, 2022, 9:40 p.m. UTC

From: Wei Yang <[e-mail]>
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.

Link: https://lkml.kernel.org/r/[e-mail]
Signed-off-by: Wei Yang <[e-mail]>
Reviewed-by: Muchun Song <[e-mail]>
Acked-by: Michal Hocko <[e-mail]>
Reviewed-by: Roman Gushchin <[e-mail]>
Reviewed-by: Mike Rapoport <[e-mail]>
Reviewed-by: Shakeel Butt <[e-mail]>
Cc: Roman Gushchin <[e-mail]>
Cc: Johannes Weiner <[e-mail]>
Cc: Suren Baghdasaryan <[e-mail]>
Cc: Vladimir Davydov <[e-mail]>
Cc: Vlastimil Babka <[e-mail]>
Cc: Yang Shi <[e-mail]>
Signed-off-by: Andrew Morton <[e-mail]>
---

 mm/memcontrol.c |    2 --
 1 file changed, 2 deletions(-)

Patch

--- a/mm/memcontrol.c~mm-memcg-mem_cgroup_per_node-is-already-set-to-0-on-allocation
+++ a/mm/memcontrol.c
@@ -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;