On 01/16/2013 01:29 PM, Andrew Morton wrote: >> >> Yes. If SRAT support is available, all memory which enabled hotpluggable >> bit are managed by ZONEMOVABLE. But performance degradation may >> occur by NUMA because we can only allocate anonymous page and page-cache >> from these memory. >> >> In this case, if user cannot change SRAT information, user needs a way to >> select/set removable memory manually. > > If I understand this correctly you mean that once SRAT parsing is > implemented, the user can use movablecore_map to override that SRAT > parsing, yes? That movablecore_map will take precedence over SRAT? > Yes, but we still need a higher-level user interface which specifies which nodes, not which memory ranges, should be movable. That is the policy granularity that is actually appropriate for the administrator (trading off performance vs reliability.) -hpa -- 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/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>