On 5 May 2023 10:11:41 -0700 Douglas Anderson <dianders@xxxxxxxxxxxx> > What type of evidence are you looking for? Because kswapd is responsible for maintaining watermarks, there is no memory pressure if it decides to take a nap. Anyway defragmentation can not make forward progress without enough free pages, see kswapd_is_running() in should_proactive_compact_node(). > When I'm reproducing these > problems, I'm running a test that specifically puts the system under > memory pressure by opening up lots of tabs in the Chrome browser. When > I start seeing these printouts, I can take a look at the system and I > can see that it's pretty much constantly swapping in and swapping out. Now trun to what is important. The constant swapin and swapout say more tabs are opened than designed, and simply closing enough tabs is a better fix, because fix like this one fails again with 20 more tabs opened for instance.
