On Fri 10-03-17 14:07:16, Mel Gorman wrote: > On Thu, Mar 09, 2017 at 05:46:16PM -0600, Zi Yan wrote: [...] > > I understand your concern on CPU utilization impact. I think checking > > CPU utilization and only using idle CPUs could potentially avoid this > > problem. > > > > That will be costly to detect actually. It would require poking into the > scheduler core and incurring a number of cache misses for a race-prone > operation that may not succeed. Even if you do it, it'll still be > brought up that the serialised case should be optimised first. do not forget that seeing idle cpus is not a sufficient criterion to use it for parallel migration. There might be other policies you are not aware of from the MM code to keep them idle (power saving and who knows what else). Developing a reasonable strategy for spreading the load to different CPUs is really hard, much harder than you can imaging I suspect (just look at how hard it was and I long it took to get to a reasonable scheduler driven frequency scaling/power governors). -- Michal Hocko SUSE Labs -- 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>
