From: Michal Hocko <mhocko@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Wei Yang <richardw.yang@linux.intel.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
rientjes@google.com
Subject: Re: [Patch v4] mm/vmscan.c: remove cpu online notification for now
Date: Thu, 20 Feb 2020 08:52:18 +0100 [thread overview]
Message-ID: <20200220075218.GA20509@dhcp22.suse.cz> (raw)
In-Reply-To: <20200219120810.c7677fa58594f5423549f59d@linux-foundation.org>
On Wed 19-02-20 12:08:10, Andrew Morton wrote:
> On Wed, 19 Feb 2020 06:44:22 +0800 Wei Yang <richardw.yang@linux.intel.com> wrote:
>
> > kswapd kernel thread starts either with a CPU affinity set to the full
> > cpu mask of its target node or without any affinity at all if the node
> > is CPUless. There is a cpu hotplug callback (kswapd_cpu_online) that
> > implements an elaborate way to update this mask when a cpu is onlined.
> >
> > It is not really clear whether there is any actual benefit from this
> > scheme. Completely CPU-less NUMA nodes rarely gain a new CPU during
> > runtime.
>
> This is the case across all platforms, all architectures, all users for
> the next N years? I'm surprised that we know this with sufficient
> confidence. Can you explain how you came to make this assertion?
CPUless NUMA nodes are quite rare - mostly ppc with crippled LPARs.
I am not aware those would dynamically get CPUs for those nodes later in
the runtime. Maybe they do but we would like to learn about that. A
missing cpu mask is not going cause any fatal problems anyway.
As the changelog states the callback can be reintroduced with a sign of
testing and usecase description. I prefer we drop this code in the mean
time as the benefit is not really clear or testable.
> > Drop the code for that reason. If there is a real usecase then
> > we can resurrect and simplify the code.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2020-02-20 7:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 22:44 Wei Yang
2020-02-19 20:08 ` Andrew Morton
2020-02-20 7:52 ` Michal Hocko [this message]
2020-02-20 17:03 ` Yang Shi
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=20200220075218.GA20509@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=richardw.yang@linux.intel.com \
--cc=rientjes@google.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