Hi Andrew,
2012/05/12 5:39, Andrew Morton wrote:
On Fri, 11 May 2012 13:46:04 +0800
Lai Jiangshan<laijs@xxxxxxxxxxxxxx> wrote:
Current ZONE_MOVABLE (kernelcore=) setting policy with boot option doesn't meet
our requirement. We need something like kernelcore_max_addr= boot option
to limit the kernelcore upper address.
Why do you need this? Please fully describe the requirement/use case.
We want to create removable node for removing a system board
which equip CPU and memory at runtime. To do this, all memory
of a node on system board must be allocated as ZONE_MOVABLE.
But current linux cannot do it.
So we create removable node by limiting the memory address of
the kernelcore by the boot option.
Thanks,
Yasuaki Ishimatsu
The memory with higher address will be migratable(movable) and they
are easier to be offline(always ready to be offline when the system don't require
so much memory).
All kernelcore_max_addr=, kernelcore= and movablecore= can be safely specified
at the same time(or any 2 of them).
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email:<a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx</a>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>