From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Nathan Lynch <nathanl@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: srikar.dronamraju@in.ibm.com, mmc@linux.ibm.com,
mwb@linux.ibm.com, julietk@linux.ibm.com
Subject: Re: [1/2] powerpc/numa: improve control of topology updates
Date: Mon, 22 Apr 2019 00:19:15 +1000 (AEST) [thread overview]
Message-ID: <44nBfW6zV9z9s5c@ozlabs.org> (raw)
In-Reply-To: <20190418185658.29751-2-nathanl@linux.ibm.com>
On Thu, 2019-04-18 at 18:56:57 UTC, Nathan Lynch wrote:
> When booted with "topology_updates=no", or when "off" is written to
> /proc/powerpc/topology_updates, NUMA reassignments are inhibited for
> PRRN and VPHN events. However, migration and suspend unconditionally
> re-enable reassignments via start_topology_update(). This is
> incoherent.
>
> Check the topology_updates_enabled flag in
> start/stop_topology_update() so that callers of those APIs need not be
> aware of whether reassignments are enabled. This allows the
> administrative decision on reassignments to remain in force across
> migrations and suspensions.
>
> Signed-off-by: Nathan Lynch <nathanl@linux.ibm.com>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/2d4d9b308f8f8dec68f6dbbff18c68ec
cheers
next prev parent reply other threads:[~2019-04-21 15:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 18:56 [PATCH 0/2] disable NUMA affinity reassignments at runtime Nathan Lynch
2019-04-18 18:56 ` [PATCH 1/2] powerpc/numa: improve control of topology updates Nathan Lynch
2019-04-21 14:19 ` Michael Ellerman [this message]
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=44nBfW6zV9z9s5c@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=julietk@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mmc@linux.ibm.com \
--cc=mwb@linux.ibm.com \
--cc=nathanl@linux.ibm.com \
--cc=srikar.dronamraju@in.ibm.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).