From: Liu Shixin <liushixin2@huawei.com>
To: David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Waiman Long <longman@redhat.com>,
Zefan Li <lizefan.x@bytedance.com>,
Christoph Lameter <cl@linux.com>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: Re: [PATCH v3 1/8] cgroup/cpuset: use hotplug_memory_notifier() directly
Date: Fri, 23 Sep 2022 09:56:36 +0800 [thread overview]
Message-ID: <b530a919-4035-cc34-0f9e-547903678423@huawei.com> (raw)
In-Reply-To: <f0675fe8-14dc-7890-357b-565c0a706932@redhat.com>
On 2022/9/23 1:56, David Hildenbrand wrote:
> On 22.09.22 16:18, Liu Shixin wrote:
>> Since patch 316346243be6 has already updated the minimum gcc version to 5.1.
>> The previous problem mentioned in patch f02c69680088 is not existed. So we
>> can now revert to use hotplug_memory_notifier() directly rather than
>> register_hotmemory_notifier().
>>
>> Signed-off-by: Liu Shixin <liushixin2@huawei.com>
>> ---
>> kernel/cgroup/cpuset.c | 7 +------
>> 1 file changed, 1 insertion(+), 6 deletions(-)
>>
>> diff --git a/kernel/cgroup/cpuset.c b/kernel/cgroup/cpuset.c
>> index b474289c15b8..0c6db6a4f427 100644
>> --- a/kernel/cgroup/cpuset.c
>> +++ b/kernel/cgroup/cpuset.c
>> @@ -3630,11 +3630,6 @@ static int cpuset_track_online_nodes(struct notifier_block *self,
>> return NOTIFY_OK;
>> }
>> -static struct notifier_block cpuset_track_online_nodes_nb = {
>> - .notifier_call = cpuset_track_online_nodes,
>> - .priority = 10, /* ??! */
>> -};
>> -
>> /**
>> * cpuset_init_smp - initialize cpus_allowed
>> *
>> @@ -3652,7 +3647,7 @@ void __init cpuset_init_smp(void)
>> cpumask_copy(top_cpuset.effective_cpus, cpu_active_mask);
>> top_cpuset.effective_mems = node_states[N_MEMORY];
>> - register_hotmemory_notifier(&cpuset_track_online_nodes_nb);
>> + hotplug_memory_notifier(cpuset_track_online_nodes, 10);
>> cpuset_migrate_mm_wq = alloc_ordered_workqueue("cpuset_migrate_mm", 0);
>> BUG_ON(!cpuset_migrate_mm_wq);
>
>
> Please don't drop Reviewed-by or Acked-by tags. Otherwise reviewers have no clue which patch they already reviewed -- and they always have little time ;)
>
Thanks for your reminder, I'll keep it in mind.
next prev parent reply other threads:[~2022-09-23 1:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 14:18 [PATCH v3 0/8] mm: Use hotplug_memory_notifier() instead of register_hotmemory_notifier() Liu Shixin
2022-09-22 14:18 ` [PATCH v3 1/8] cgroup/cpuset: use hotplug_memory_notifier() directly Liu Shixin
2022-09-22 17:56 ` David Hildenbrand
2022-09-23 1:56 ` Liu Shixin [this message]
2022-09-22 14:18 ` [PATCH v3 2/8] fs/proc/kcore.c: " Liu Shixin
2022-09-22 14:18 ` [PATCH v3 3/8] mm/slub.c: " Liu Shixin
2022-09-22 14:19 ` [PATCH v3 4/8] mm/mmap: " Liu Shixin
2022-09-22 14:19 ` [PATCH v3 5/8] mm/mm_init.c: " Liu Shixin
2022-09-22 14:19 ` [PATCH v3 6/8] ACPI: HMAT: " Liu Shixin
2022-09-22 14:19 ` [PATCH v3 7/8] memory: remove unused register_hotmemory_notifier() Liu Shixin
2022-09-22 14:19 ` [PATCH v3 8/8] memory: move hotplug memory notifier priority to same file for easy sorting Liu Shixin
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=b530a919-4035-cc34-0f9e-547903678423@huawei.com \
--to=liushixin2@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan.x@bytedance.com \
--cc=longman@redhat.com \
--cc=wangkefeng.wang@huawei.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