Re: [RFC PATCH 2/2] mm, memory_hotplug: drop CONFIG_MOVABLE_NODE

From: Reza Arbab
Date: Wed May 24 2017 - 17:52:01 EST


On Wed, May 24, 2017 at 02:24:11PM +0200, Michal Hocko wrote:
20b2f52b73fe ("numa: add CONFIG_MOVABLE_NODE for movable-dedicated
node") has introduced CONFIG_MOVABLE_NODE without a good explanation on
why it is actually useful. It makes a lot of sense to make movable node
semantic opt in but we already have that because the feature has to be
explicitly enabled on the kernel command line. A config option on top
only makes the configuration space larger without a good reason. It also
adds an additional ifdefery that pollutes the code. Just drop the config
option and make it de-facto always enabled. This shouldn't introduce any
change to the semantic.

Acked-by: Reza Arbab <arbab@xxxxxxxxxxxxxxxxxx>

--
Reza Arbab