On Wed, 22 Jun 2016, Andrew Morton wrote: > On Tue, 21 Jun 2016 18:22:49 -0700 (PDT) David Rientjes <rientjes@xxxxxxxxxx> wrote: > > > If the memory compaction free scanner cannot successfully split a free > > page (only possible due to per-zone low watermark), terminate the free > > scanner rather than continuing to scan memory needlessly. If the > > watermark is insufficient for a free page of order <= cc->order, then > > terminate the scanner since all future splits will also likely fail. > > > > This prevents the compaction freeing scanner from scanning all memory on > > very large zones (very noticeable for zones > 128GB, for instance) when > > all splits will likely fail while holding zone->lock. > > > > This collides pretty heavily with Joonsoo's "mm/compaction: split > freepages without holding the zone lock". > Sorry if it wasn't clear, but I was proposing this patch for 4.7 inclusion and Vlastimil agreed we should ask for that. Joonsoo said he was prepared to rebase on top of that. Is mm-compaction-split-freepages-without-holding-the-zone-lock.patch and friends going into 4.7 or are we deferring this fix until 4.8? compaction_alloc() iterating a 128GB zone has been benchmarked to take over 400ms on some systems whereas any free page isolated and ready to be split ends up failing in split_free_page() because of the low watermark check and thus the iteration continues. The next time compaction occurs, the freeing scanner will likely start at the end of the zone again since no success was made previously and we get the same lengthy iteration until the zone is brought above the low watermark. All thp page faults can take >400ms in such a state without this fix. -- 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>