From: Miaohe Lin <linmiaohe@huawei.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: <akpm@linux-foundation.org>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>,
Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
Subject: Re: [PATCH] memory tier: Use helper function destroy_memory_type()
Date: Mon, 3 Jul 2023 11:25:02 +0800 [thread overview]
Message-ID: <7da17dc7-b226-3a22-b13b-c2e6c6365c5d@huawei.com> (raw)
In-Reply-To: <87y1jxitg9.fsf@yhuang6-desk2.ccr.corp.intel.com>
On 2023/7/3 11:07, Huang, Ying wrote:
> Miaohe Lin <linmiaohe@huawei.com> writes:
>
>> On 2023/7/3 10:28, Huang, Ying wrote:
>>> Miaohe Lin <linmiaohe@huawei.com> writes:
>>>
>>>> Use helper function destroy_memory_type() to release memtype instead
>>>> of open code it to help improve code readability a bit. No functional
>>>> change intended.
>>>>
>>>> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
>>>> ---
>>>> mm/memory-tiers.c | 2 +-
>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/mm/memory-tiers.c b/mm/memory-tiers.c
>>>> index e593e56e530b..0b8b76078c12 100644
>>>> --- a/mm/memory-tiers.c
>>>> +++ b/mm/memory-tiers.c
>>>> @@ -587,7 +587,7 @@ void clear_node_memory_type(int node, struct memory_dev_type *memtype)
>>>> */
>>>> if (!node_memory_types[node].map_count) {
>>>> node_memory_types[node].memtype = NULL;
>>>> - kref_put(&memtype->kref, release_memtype);
>>>> + destroy_memory_type(memtype);
>>>
>>> Not need to be changed in this patch. It appears that
>>> destroy_memory_type() isn't a very good name, because we usually will
>>> not free the memory_type here. Rename it to "put_memory_type()"?
>>
>> Do you mean rename destroy_memory_type to put_memory_type in a
>> separate patch?
>
> Yes.
>
>> This sounds reasonable to me. But destroy_memory_type is a
>> EXPORT_SYMBOL_GPL symbol, is it fine to do the rename work?
>
> I think so. This isn't a kernel ABI. And not many people use it now.
Will do it. Thanks for your advice.
>
> Best Regards,
> Huang, Ying
>
>
> .
>
prev parent reply other threads:[~2023-07-03 3:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 12:10 Miaohe Lin
2023-07-03 2:28 ` Huang, Ying
2023-07-03 2:53 ` Miaohe Lin
2023-07-03 3:07 ` Huang, Ying
2023-07-03 3:25 ` Miaohe Lin [this message]
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=7da17dc7-b226-3a22-b13b-c2e6c6365c5d@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ying.huang@intel.com \
/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