On Wed, 19 Feb 2020 10:25:22 -0800 Sultan Alsawaf <sultan@xxxxxxxxxxxxxxx> wrote: > Keeping kswapd running when all the failed allocations that invoked it > are satisfied incurs a high overhead due to unnecessary page eviction > and writeback, as well as spurious VM pressure events to various > registered shrinkers. When kswapd doesn't need to work to make an > allocation succeed anymore, stop it prematurely to save resources. Seems sensible. Please fully describe the userspace-visible runtime effects of this change?
