From: Nathan Lynch <nathanl@linux•ibm.com>
To: linuxppc-dev@lists•ozlabs.org
Cc: srikar.dronamraju@in•ibm.com, mmc@linux•ibm.com,
mwb@linux•ibm.com, julietk@linux•ibm.com
Subject: [PATCH 0/2] disable NUMA affinity reassignments at runtime
Date: Thu, 18 Apr 2019 13:56:56 -0500 [thread overview]
Message-ID: <20190418185658.29751-1-nathanl@linux.ibm.com> (raw)
Changing cpu <-> node relationships at runtime, as the pseries
platform code attempts to do for LPM, PRRN, and VPHN is essentially
unsupported by core subsystems. [1]
While more significant changes (i.e. discarding all that code) likely
are in store, these patches are a minimally invasive way to disable
the problem behavior in a way that should be suitable for backporting
to -stable and distros, and is an improvement on the current
situation.
Note: this doesn't affect use of VPHN at boot time for detecting
shared processor node assignments. Only runtime VPHN-initiated
reassignments are disabled.
[1] E.g. see the discussion here:
https://lore.kernel.org/lkml/20180831115350.GC8437@linux.vnet.ibm.com/T/#u
Nathan Lynch (2):
powerpc/numa: improve control of topology updates
powerpc/numa: document topology_updates_enabled, disable by default
arch/powerpc/mm/numa.c | 32 ++++++++++++++++++++++----------
1 file changed, 22 insertions(+), 10 deletions(-)
--
2.20.1
next reply other threads:[~2019-04-18 19:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 18:56 Nathan Lynch [this message]
2019-04-18 18:56 ` [PATCH 1/2] powerpc/numa: improve control of topology updates Nathan Lynch
2019-04-21 14:19 ` [1/2] " Michael Ellerman
2019-04-18 18:56 ` [PATCH 2/2] powerpc/numa: document topology_updates_enabled, disable by default Nathan Lynch
2019-04-18 20:30 ` [PATCH 0/2] disable NUMA affinity reassignments at runtime Michal Suchánek
2019-04-18 22:37 ` Nathan Lynch
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=20190418185658.29751-1-nathanl@linux.ibm.com \
--to=nathanl@linux$(echo .)ibm.com \
--cc=julietk@linux$(echo .)ibm.com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mmc@linux$(echo .)ibm.com \
--cc=mwb@linux$(echo .)ibm.com \
--cc=srikar.dronamraju@in$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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