Hi > My tree uses compaction in a fine way inside kswapd too and tons of > systems are running without lumpy and floods of order 9 allocations > with only compaction (in direct reclaim and kswapd) without the > slighest problem. Furthermore I extended compaction for all > allocations not just that PAGE_ALLOC_COSTLY_ORDER (maybe I already > removed all PAGE_ALLOC_COSTLY_ORDER checks?). There's no good reason > not to use compaction for every allocation including 1,2,3, and things > works fine this way. Interesting. I parsed this you have compaction improvement. If so, can you please post them? Generically, 1) improve the feature 2) remove unused one is safety order. In the other hand, reverse order seems to has regression risk. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>