From: Oscar Salvador <osalvador@suse.de>
To: Dave Hansen <dave.hansen@intel.com>
Cc: "Huang, Ying" <ying.huang@intel.com>,
Abhishek Goel <huntbag@linux.vnet.ibm.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Zi Yan <ziy@nvidia.com>, David Hildenbrand <david@redhat.com>,
Yang Shi <yang.shi@linux.alibaba.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH -V11 2/9] mm/migrate: update node demotion order on hotplug events
Date: Tue, 8 Mar 2022 19:56:59 +0100 [thread overview]
Message-ID: <Yiem+4YbComC0EGC@localhost.localdomain> (raw)
In-Reply-To: <86383ac9-e5f2-1a2e-dd19-02e39714a3fd@intel.com>
On Tue, Mar 08, 2022 at 09:07:20AM -0800, Dave Hansen wrote:
> On 3/8/22 02:27, Oscar Salvador wrote:
> > @@ -2043,7 +2044,12 @@ static void __init init_cpu_node_state(void)
> > static int vmstat_cpu_online(unsigned int cpu)
> > {
> > refresh_zone_stat_thresholds();
> > - node_set_state(cpu_to_node(cpu), N_CPU);
> > +
> > + if (!node_state(cpu_to_node(cpu), N_CPU)) {
> > + node_set_state(cpu_to_node(cpu), N_CPU);
> > + set_migration_target_nodes();
> > + }
> > +
> > return 0;
> > }
> >
> > @@ -2066,6 +2072,8 @@ static int vmstat_cpu_dead(unsigned int cpu)
> > return 0;
> >
> > node_clear_state(node, N_CPU);
> > + set_migration_target_nodes();
> > +
> > return 0;
> > }
>
> Yeah, those callbacks do look like they're reinventing the wheel. This
> is a much more direct way of doing it.
Then let me play a bit more with it and I can cook a patch unless
someone feels strong against it.
Thanks
--
Oscar Salvador
SUSE Labs
next prev parent reply other threads:[~2022-03-08 18:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 6:39 [PATCH -V11 1/9] mm/numa: automatically generate node migration order Huang Ying
2021-07-21 6:39 ` [PATCH -V11 2/9] mm/migrate: update node demotion order on hotplug events Huang Ying
2022-02-23 23:02 ` Abhishek Goel
2022-02-24 0:05 ` Dave Hansen
2022-02-24 23:37 ` Abhishek Goel
2022-02-25 0:49 ` Dave Hansen
2022-02-25 2:32 ` Huang, Ying
2022-02-25 20:35 ` Abhishek Goel
2022-03-08 10:27 ` Oscar Salvador
2022-03-08 17:07 ` Dave Hansen
2022-03-08 18:56 ` Oscar Salvador [this message]
2022-03-09 0:29 ` Huang, Ying
2021-07-21 6:39 ` [PATCH -V11 3/9] mm/migrate: enable returning precise migrate_pages() success count Huang Ying
2021-07-21 6:39 ` [PATCH -V11 4/9] mm/migrate: demote pages during reclaim Huang Ying
2021-07-21 21:11 ` Zi Yan
2021-07-21 6:39 ` [PATCH -V11 5/9] mm/vmscan: add page demotion counter Huang Ying
2021-07-21 21:13 ` Zi Yan
2021-07-21 6:39 ` [PATCH -V11 6/9] mm/vmscan: add helper for querying ability to age anonymous pages Huang Ying
2021-07-21 21:15 ` Zi Yan
2021-07-21 6:39 ` [PATCH -V11 7/9] mm/vmscan: Consider anonymous pages without swap Huang Ying
2021-07-21 21:21 ` Zi Yan
2021-07-21 6:39 ` [PATCH -V11 8/9] mm/vmscan: never demote for memcg reclaim Huang Ying
2021-07-21 21:38 ` Zi Yan
2021-07-21 21:58 ` Dave Hansen
2021-07-21 21:59 ` Zi Yan
2021-07-21 22:03 ` Yang Shi
2021-07-21 6:39 ` [PATCH -V11 9/9] mm/migrate: add sysfs interface to enable reclaim migration Huang Ying
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=Yiem+4YbComC0EGC@localhost.localdomain \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=huntbag@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=yang.shi@linux.alibaba.com \
--cc=ying.huang@intel.com \
--cc=ziy@nvidia.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;
as well as URLs for NNTP newsgroup(s).