From: Oscar Salvador <firstname.lastname@example.org>
To: Andrew Morton <email@example.com>
Cc: Dave Hansen <firstname.lastname@example.org>,
"Huang, Ying" <email@example.com>,
Abhishek Goel <firstname.lastname@example.org>,
Baolin Wang <email@example.com>,
Subject: Re: [PATCH v2] mm: Only re-generate demotion targets when a numa node changes its N_CPU state
Date: Fri, 11 Mar 2022 10:23:44 +0100 [thread overview]
Message-ID: <YisVIIGcSgi7NL8N@localhost.localdomain> (raw)
On Thu, Mar 10, 2022 at 06:39:51PM -0800, Andrew Morton wrote:
> What I'm not getting here (as so often happens) is a sense of how badly
> this affects our users. Does anyone actually hotplug frequently enough
> to care?
Well, I would not say it is critical, it just regresses the time
hotplug operations take. How bad is that? I guess it depends.
Memory hotplug operations are already slow per se, so I would say
expectations are not that high.
But it speeds up the process, that is for sure.
e.g: In a system with 144 CPUs and 2 Numa-nodes,
gets called exactly 144 times at boot time(one per every time a CPU is
brought up), where only 2 calls would suffice, so you can get an idea.
> If "yes" then I'm inclined to merge this up for 5.18 with a cc:stable.
> Not for 5.17 because it's late and things are looking rather creaky
> And I'll add a
> Fixes: 884a6e5d1f93b ("mm/migrate: update node demotion order on hotplug events")
> which is that patch's fourth such bouquet.
next prev parent reply other threads:[~2022-03-11 9:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 12:07 [PATCH v2] mm: Only re-generate demotion targets when a numa node changes its N_CPU state Oscar Salvador
2022-03-11 1:33 ` Baolin Wang
2022-03-11 2:24 ` Huang, Ying
2022-03-11 8:39 ` Oscar Salvador
2022-03-14 1:03 ` Huang, Ying
2022-03-14 15:13 ` Oscar Salvador
2022-03-14 15:20 ` Dave Hansen
2022-03-15 6:13 ` Oscar Salvador
2022-03-15 6:31 ` Huang, Ying
2022-03-11 2:39 ` Andrew Morton
2022-03-11 9:23 ` Oscar Salvador [this message]
2022-03-11 17:10 ` Dave Hansen
2022-03-14 9:09 ` Abhishek Goel
2022-03-11 5:06 ` Huang, Ying
2022-03-11 9:17 ` Oscar Salvador
2022-03-14 3:09 ` Huang, Ying
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.