On Wed, Feb 19, 2020 at 09:45:13PM +0000, Mel Gorman wrote: > This could be watermark boosting run wild again. Can you test with > sysctl vm.watermark_boost_factor=0 or the following patch? (preferably > both to compare and contrast). I can test that, but something to note is that I've been doing equal testing with this on 4.4, which exhibits the same behavior, and that kernel doesn't have watermark boosting in it, as far as I can tell. I don't think what we're addressing here is a "bug", but rather something fundamental about how we've been thinking about kswapd lifetime. The argument here is that it's not coherent to be letting kswapd run as it does, and instead gating it on outstanding allocation requests provides much more reasonable behavior, given real workloads and use patterns. Does that make sense and seem reasonable? Sultan
