From: xiujianfeng <xiujianfeng@huawei.com>
To: Michal Hocko <mhocko@suse.com>
Cc: <hannes@cmpxchg.org>, <roman.gushchin@linux.dev>,
<shakeel.butt@linux.dev>, <muchun.song@linux.dev>,
<akpm@linux-foundation.org>, <cgroups@vger.kernel.org>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 -next] mm: memcg: make alloc_mem_cgroup_per_node_info() return bool
Date: Tue, 7 May 2024 21:31:39 +0800 [thread overview]
Message-ID: <10484734-13e6-4c56-d7dc-6c4cf74bd8de@huawei.com> (raw)
In-Reply-To: <ZjooSnQ_vS30EXCT@tiehlicka>
On 2024/5/7 21:10, Michal Hocko wrote:
> On Tue 07-05-24 11:08:32, Xiu Jianfeng wrote:
>> Currently alloc_mem_cgroup_per_node_info() returns 1 if failed,
>> make it return bool, false for failure and true for success.
>
> This describes what the patch does rather than why it is doing that.
> The former is clear from the diff while the motivation for this change
> is unclear. I would propose something like:
>
> alloc_mem_cgroup_per_node_info() returns int that doesn't map to any
> errno error code. The only existing caller doesn't really need an error
> code so change the the function to return bool (true on success) because
> this is slightly less confusing and more consistent with the other code.
Thanks, it looks much better now.
>
>> Signed-off-by: Xiu Jianfeng <xiujianfeng@huawei.com>
>
> With changelog clarified feel free to add
> Acked-by: Michal Hocko <mhocko@suse.com>
>
>> ---
>> mm/memcontrol.c | 10 +++++-----
>> 1 file changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
>> index d11536ef59ef..69d70feb8e68 100644
>> --- a/mm/memcontrol.c
>> +++ b/mm/memcontrol.c
>> @@ -5653,13 +5653,13 @@ struct mem_cgroup *mem_cgroup_get_from_ino(unsigned long ino)
>> }
>> #endif
>>
>> -static int alloc_mem_cgroup_per_node_info(struct mem_cgroup *memcg, int node)
>> +static bool alloc_mem_cgroup_per_node_info(struct mem_cgroup *memcg, int node)
>> {
>> struct mem_cgroup_per_node *pn;
>>
>> pn = kzalloc_node(sizeof(*pn), GFP_KERNEL, node);
>> if (!pn)
>> - return 1;
>> + return false;
>>
>> pn->lruvec_stats = kzalloc_node(sizeof(struct lruvec_stats), GFP_KERNEL,
>> node);
>> @@ -5675,11 +5675,11 @@ static int alloc_mem_cgroup_per_node_info(struct mem_cgroup *memcg, int node)
>> pn->memcg = memcg;
>>
>> memcg->nodeinfo[node] = pn;
>> - return 0;
>> + return true;
>> fail:
>> kfree(pn->lruvec_stats);
>> kfree(pn);
>> - return 1;
>> + return false;
>> }
>>
>> static void free_mem_cgroup_per_node_info(struct mem_cgroup *memcg, int node)
>> @@ -5751,7 +5751,7 @@ static struct mem_cgroup *mem_cgroup_alloc(struct mem_cgroup *parent)
>> }
>>
>> for_each_node(node)
>> - if (alloc_mem_cgroup_per_node_info(memcg, node))
>> + if (!alloc_mem_cgroup_per_node_info(memcg, node))
>> goto fail;
>>
>> if (memcg_wb_domain_init(memcg, GFP_KERNEL))
>> --
>> 2.34.1
>>
>
next prev parent reply other threads:[~2024-05-07 13:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 11:08 Xiu Jianfeng
2024-05-07 13:10 ` Michal Hocko
2024-05-07 13:31 ` xiujianfeng [this message]
2024-05-07 16:09 ` Roman Gushchin
2024-05-09 14:05 ` Johannes Weiner
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=10484734-13e6-4c56-d7dc-6c4cf74bd8de@huawei.com \
--to=xiujianfeng@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox