Hi HPA and Tang,
2012/11/27 17:49, H. Peter Anvin wrote:
On 11/27/2012 12:29 AM, Tang Chen wrote:
Another approach is like the following:
movable_node = 1,3-5,8
This could set all the memory on the nodes to be movable. And the rest
of memory works as usual. But movablecore_map is more flexible.
... but *much* harder for users, so movable_node is better in most cases.
It seems that movable_node is easier to use than movablecore_map.
But I do not think movable_node is better because the node number is set
by OS and changed easily.
For exmaple:
If system has 4 nodes and we set moveble_node=2, we can hot remove node2.
node0 node1 node2 node3
+-----+ +-----+ +-----+ +-----+
| | | | |/////| | |
| | | | |/////| | |
| | | | |/////| | |
| | | | |/////| | |
+-----+ +-----+ +-----+ +-----+
movable
node
But if we hot remove node2 and reboot the system, node3 is changed to node2
and set to movable node.
node0 node1 node2
+-----+ +-----+ +-----+
| | | | |/////|
| | | | |/////|
| | | | |/////|
| | | | |/////|
+-----+ +-----+ +-----+
movable
node
Originally, node3 is not movable node. Changing the node attribution to
movable node is not intended. So if user uses movable_node,
user must confirm whether boot option is correctly set at hotplug.
But memory range is set by firmware and not changed. So if we set node2
as movable node by movablecore_map, the issue does not occur.
Thanks,
Yasuaki Ishimatsu
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
