From: Shakeel Butt <shakeelb@google.com>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Roman Gushchin <guro@fb.com>, Vlastimil Babka <vbabka@suse.cz>,
Matthew Wilcox <willy@infradead.org>,
Muchun Song <songmuchun@bytedance.com>,
Yang Shi <shy828301@gmail.com>,
Suren Baghdasaryan <surenb@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Cgroups <cgroups@vger.kernel.org>, Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH 2/4] mm/memcg: mem_cgroup_per_node is already set to 0 on allocation
Date: Sun, 16 Jan 2022 11:24:03 -0800 [thread overview]
Message-ID: <CALvZod5ycSmk7URBoLGGJAiyjGQ1E0HR2RnJ-3uZai=t+KpEKA@mail.gmail.com> (raw)
In-Reply-To: <20220111010302.8864-2-richard.weiyang@gmail.com>
On Mon, Jan 10, 2022 at 5:03 PM Wei Yang <richard.weiyang@gmail.com> wrote:
>
> 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: Shakeel Butt <shakeelb@google.com>
WARNING: multiple messages have this Message-ID (diff)
From: Shakeel Butt <shakeelb-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
To: Wei Yang <richard.weiyang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>,
Michal Hocko <mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Vladimir Davydov
<vdavydov.dev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
Roman Gushchin <guro-b10kYP2dOMg@public.gmane.org>,
Vlastimil Babka <vbabka-AlSwsSmVLrQ@public.gmane.org>,
Matthew Wilcox <willy-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
Muchun Song <songmuchun-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org>,
Yang Shi <shy828301-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Suren Baghdasaryan
<surenb-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Cgroups <cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux MM <linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org>
Subject: Re: [PATCH 2/4] mm/memcg: mem_cgroup_per_node is already set to 0 on allocation
Date: Sun, 16 Jan 2022 11:24:03 -0800 [thread overview]
Message-ID: <CALvZod5ycSmk7URBoLGGJAiyjGQ1E0HR2RnJ-3uZai=t+KpEKA@mail.gmail.com> (raw)
In-Reply-To: <20220111010302.8864-2-richard.weiyang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Mon, Jan 10, 2022 at 5:03 PM Wei Yang <richard.weiyang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> kzalloc_node() would set data to 0, so it's not necessary to set it
> again.
>
> Signed-off-by: Wei Yang <richard.weiyang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Reviewed-by: Shakeel Butt <shakeelb-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
next prev parent reply other threads:[~2022-01-16 19:24 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 1:02 [PATCH 1/4] mm/memcg: use NUMA_NO_NODE to indicate allocation from unspecified node Wei Yang
2022-01-11 1:02 ` Wei Yang
2022-01-11 1:03 ` [PATCH 2/4] mm/memcg: mem_cgroup_per_node is already set to 0 on allocation Wei Yang
2022-01-11 2:25 ` Muchun Song
2022-01-11 2:25 ` Muchun Song
2022-01-11 8:41 ` Michal Hocko
2022-01-11 18:06 ` Roman Gushchin
2022-01-11 18:06 ` Roman Gushchin
2022-01-14 11:08 ` Mike Rapoport
2022-01-16 19:24 ` Shakeel Butt [this message]
2022-01-16 19:24 ` Shakeel Butt
2022-01-11 1:03 ` [PATCH 3/4] mm/memcg: retrieve parent memcg from css.parent Wei Yang
2022-01-11 1:03 ` Wei Yang
2022-01-11 3:12 ` Muchun Song
2022-01-11 3:12 ` Muchun Song
2022-01-11 8:43 ` Michal Hocko
2022-01-11 18:09 ` Roman Gushchin
2022-01-11 18:09 ` Roman Gushchin
2022-01-12 0:24 ` Wei Yang
2022-01-12 0:24 ` Wei Yang
2022-01-16 19:54 ` Shakeel Butt
2022-01-16 19:54 ` Shakeel Butt
2022-01-11 1:03 ` [PATCH 4/4] mm/memcg: refine mem_cgroup_threshold_ary->current_threshold calculation Wei Yang
2022-01-11 1:03 ` Wei Yang
2022-01-11 8:44 ` Michal Hocko
2022-01-11 18:23 ` Roman Gushchin
2022-01-11 18:23 ` Roman Gushchin
2022-01-12 0:25 ` Wei Yang
2022-01-12 0:25 ` Wei Yang
2022-01-11 2:23 ` [PATCH 1/4] mm/memcg: use NUMA_NO_NODE to indicate allocation from unspecified node Muchun Song
2022-01-11 2:23 ` Muchun Song
2022-01-11 8:40 ` Michal Hocko
2022-01-11 8:40 ` Michal Hocko
2022-01-12 0:46 ` Wei Yang
2022-01-12 0:46 ` Wei Yang
2022-01-12 8:56 ` Michal Hocko
2022-01-12 8:56 ` Michal Hocko
2022-01-14 0:29 ` Wei Yang
2022-01-14 0:29 ` Wei Yang
2022-01-14 8:51 ` Michal Hocko
2022-01-14 8:51 ` Michal Hocko
2022-01-15 22:10 ` Wei Yang
2022-01-15 22:10 ` Wei Yang
2022-01-16 19:23 ` Shakeel Butt
2022-01-16 19:23 ` Shakeel Butt
2022-01-11 18:05 ` Roman Gushchin
2022-01-11 18:05 ` Roman Gushchin
2022-01-14 11:07 ` Mike Rapoport
2022-01-14 11:07 ` Mike Rapoport
2022-01-31 1:47 ` Wei Yang
2022-01-31 1:47 ` Wei Yang
2022-01-31 22:36 ` Andrew Morton
2022-01-31 22:36 ` Andrew Morton
2022-02-01 0:42 ` Wei Yang
2022-02-01 0:42 ` Wei Yang
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='CALvZod5ycSmk7URBoLGGJAiyjGQ1E0HR2RnJ-3uZai=t+KpEKA@mail.gmail.com' \
--to=shakeelb@google.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=richard.weiyang@gmail.com \
--cc=shy828301@gmail.com \
--cc=songmuchun@bytedance.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=vdavydov.dev@gmail.com \
--cc=willy@infradead.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.