On Mon, Mar 19, 2012 at 02:39:31PM +0100, Peter Zijlstra wrote: > On Mon, 2012-03-19 at 14:04 +0100, Andrea Arcangeli wrote: > > In implementation terms the scheduler is simplified and it won't work > > as well as it should with massive CPU overcommit. But I had to take > > shortcuts to keep the complexity down to O(N) where N is the number of > > CPUS > > Yeah I saw that, you essentially put a nr_cpus loop inside schedule(), > obviously that's not going to ever happen. lol Would be fun if such a simplification would still perform better than your code :). Yeah I'll try to fix that but it's massively complex and frankly benchmarking wise it won't help much fixing that... so it's beyond the end of my todo list. -- 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>