* Zhang Yanfei <[email protected]> wrote:
> @@ -153,11 +153,18 @@ config MOVABLE_NODE
> help
> Allow a node to have only movable memory. Pages used by the kernel,
> such as direct mapping pages cannot be migrated. So the corresponding
> + memory device cannot be hotplugged. This option allows the following
> + two things:
> + - When the system is booting, node full of hotpluggable memory can
> + be arranged to have only movable memory so that the whole node can
> + be hotplugged. (need movable_node boot option specified).
So this is _exactly_ what I complained about earlier: why is the
movable_node boot option needed to get that extra functionality? It's
clearly not just a drop-in substitute to CONFIG_MOVABLE_NODE but extends
its functionality, right?
Boot options are _very_ poor user interface. If you don't want to enable
it by default then turn this sub-functionality into
CONFIG_MOVABLE_NODE_AUTO and keep it default-off - but don't pretend that
this is only about CONFIG_MOVABLE_NODE alone - it isnt: as described above
the 'movable_node' is needed for the full functionality to be available!
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
