On Thu, Nov 20, 2014 at 12:10:30AM +0100, Vlastimil Babka wrote: > > Is this fixed in a later kernel? I haven't tested yet. > > As I said, recent kernels received many compaction performance tuning patches, > and reclaim as well. I would recommend trying them, if it's possible. > > You mention 3.10.0-123.9.3.el7.x86_64 which I have no idea how it relates to > upstream stable kernel. Upstream version 3.10.44 received several compaction > fixes that I'd deem critical for compaction to work as intended, and lack of > them could explain your problems: > > mm: compaction: reset cached scanner pfn's before reading them > commit d3132e4b83e6bd383c74d716f7281d7c3136089c upstream. > > mm: compaction: detect when scanners meet in isolate_freepages > commit 7ed695e069c3cbea5e1fd08f84a04536da91f584 upstream. > > mm/compaction: make isolate_freepages start at pageblock boundary > commit 49e068f0b73dd042c186ffa9b420a9943e90389a upstream. > > You might want to check if those are included in your kernel package, and/or try > upstream stable 3.10 (if you can't use the latest for some reason). Excellent, thankyou. I realised there were a lot of changes but this list of specific fixes might help narrow down the actual cause here. I've just built a kernel that's exactly the same as the exploding one with just these three patches and will be back tomorrow with the results of testing.
Attachment:
pgp2RzF9cvOi0.pgp
Description: PGP signature