On Thu, Jan 17, 2019 at 04:16:54PM +0100, Vlastimil Babka wrote: > On 1/4/19 1:50 PM, Mel Gorman wrote: > > Pageblocks are marked for skip when no pages are isolated after a scan. > > However, it's possible to hit corner cases where the migration scanner > > gets stuck near the boundary between the source and target scanner. Due > > to pages being migrated in blocks of COMPACT_CLUSTER_MAX, pages that > > are migrated can be reallocated before the pageblock is complete. The > > pageblock is not necessarily skipped so it can be rescanned multiple > > times. Similarly, a pageblock with some dirty/writeback pages may fail > > to isolate and be rescanned until writeback completes which is wasteful. > > ^ migrate? If we failed to isolate, then it wouldn't bump nr_isolated. > Wonder if we could do better checks and not isolate pages that cannot be at the > moment migrated anyway. > Potentially but it would be considered a layering violation. There may be per-fs reasons why a page cannot migrate and no matter how well we check, there will be race conditions. > > The fault latency reduction is large and while the THP allocation > > success rate is only slightly higher, it's already high at this > > point of the series. > > > > Compaction migrate scanned 60718343.00 31772603.00 > > Compaction free scanned 933061894.00 63267928.00 > > Hm I thought the order of magnitude difference between migrate and free scanned > was already gone at this point as reported in the previous 2 patches. There are corner cases that mean there can be large differences for a single run. In some cases it doesn't matter but this one might have been unlucky. It's something that occurs less as the series progresses. > Or is this > from different system/configuration? I don't *think* so. While I had multiple machines running tests, I'm pretty sure I wrote the changelogs based on one machine and only checked the others had nothing strange. > Anyway, encouraging result. I would expect > that after "Keep migration source private to a single compaction instance" sets > the skip bits much more early and aggressively, the rescans would not happen > anymore thanks to those, even if cached pfns were not updated. > Yes and no. The corner case where the scanner gets stuck rescanning one pageblock can happen when the fast search fails. In that case, the linear scanner needs to get to the end of a pageblock and if it fails, it'll simply rescan like a lunatic. This happened specifically for pages under writeback for me. > Acked-by: Vlastimil Babka <vbabka@xxxxxxx> > Thanks -- Mel Gorman SUSE Labs
