Messages in this thread Patch in this message | | | From | Wei Yang <> | Subject | [PATCH 1/2] mm/memcg: mem_cgroup_per_node is already set to 0 on allocation | Date | Tue, 1 Feb 2022 00:46:42 +0000 |
| |
kzalloc_node() would set data to 0, so it's not necessary to set it again.
Signed-off-by: Wei Yang <richard.weiyang@gmail.com> Reviewed-by: Muchun Song <songmuchun@bytedance.com> Acked-by: Michal Hocko <mhocko@suse.com> Reviewed-by: Roman Gushchin <guro@fb.com> Reviewed-by: Mike Rapoport <rppt@linux.ibm.com> Reviewed-by: Shakeel Butt <shakeelb@google.com> --- mm/memcontrol.c | 2 -- 1 file changed, 2 deletions(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c index ea8460658550..ce7060907df2 100644 --- a/mm/memcontrol.c +++ b/mm/memcontrol.c @@ -5070,8 +5070,6 @@ static int alloc_mem_cgroup_per_node_info(struct mem_cgroup *memcg, int node) } lruvec_init(&pn->lruvec); - pn->usage_in_excess = 0; - pn->on_tree = false; pn->memcg = memcg; memcg->nodeinfo[node] = pn; -- 2.33.1
| |