* Mel Gorman <mgorman@xxxxxxx> [2013-07-15 16:20:19]: > When a preferred node is selected for a tasks there is an attempt to migrate > the task to a CPU there. This may fail in which case the task will only > migrate if the active load balancer takes action. This may never happen if Apart from load imbalance or heavily loaded cpus on the preferred node, what could be the other reasons for migration failure with migrate_task_to()? I see it almost similar to active load balance except for pushing instead of pulling tasks. If load imbalance is the only reason, do we need to retry? If the task is really so attached to memory on that node, shouldn't we getting task_numa_placement hit before the next 5 seconds? > the conditions are not right. This patch will check at NUMA hinting fault > time if another attempt should be made to migrate the task. It will only > make an attempt once every five seconds. > > Signed-off-by: Mel Gorman <mgorman@xxxxxxx> -- Thanks and Regards Srikar Dronamraju -- 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>